Content
View differences
Updated by Christophe Bliard 1 day ago
**As** a screen reader user
**I want to** listen to a list of links
**so that** I can scan the page more quickly
People using a screen reader often read list of links. In that case, a screen reader may only read Links should reflect the link text and not the surrounding text. action
Reference: [https://usability.yale.edu/digital-accessibility/accessibility-resources/accessibility-articles/accessible-links](https://usability.yale.edu/digital-accessibility/accessibility-resources/accessibility-articles/accessible-links)
Link text to enable the project-based semantic identifier is "here". It could be more helpful. Also moving the CTA at first place and the explanation after could make it easier to parse. We noticed users missing this text
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925217/content">
**Acceptance criteria**
* Proposed text is "[Enable project-based semantic identifier before migrating](about:blank). Jira uses issue identifiers consisting of a project key and a sequence number (like PRJ-123). Enable semantic identifiers in OpenProject to properly migrate them."
* What about moving it before the "This is in beta" banner?
* What about moving it in the center of the screen with everything below it being disabled?
Something a bit like this:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925221/content"> <br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** listen to a list of links
**so that** I can scan the page more quickly
People using a screen reader often read list of links. In that case, a screen reader may only read
Reference: [https://usability.yale.edu/digital-accessibility/accessibility-resources/accessibility-articles/accessible-links](https://usability.yale.edu/digital-accessibility/accessibility-resources/accessibility-articles/accessible-links)
Link text to enable the project-based semantic identifier is "here". It could be more helpful. Also moving the CTA at first place and the explanation after could make it easier to parse. We noticed users missing this text
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925217/content">
**Acceptance criteria**
* Proposed text is "[Enable project-based semantic identifier before migrating](about:blank). Jira uses issue identifiers consisting of a project key and a sequence number (like PRJ-123). Enable semantic identifiers in OpenProject to properly migrate them."
* What about moving it before the "This is in beta" banner?
* What about moving it in the center of the screen with everything below it being disabled?
Something a bit like this:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925221/content">
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._