hyperlink element (html)

Expectation: convey its role

Rationale:

A screen reader user needs to know how they can interact with the element. Voice control software might use the role to help users activate controls that do not have a visible name.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: MUST

Examples:

• A screen reader might announce a link as something like "<name>, link"
• Voice control software might let a user say something like "click link"

Expectation: convey its name

Rationale:

A screen reader user needs to know what to enter.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: MUST

Examples:

• A screen reader might announce a link as something like "<name>, link"
• Voice control software might let a user say something like "click <name>"

Expectation: convey the boundaries of the element

Rationale:

A user needs to know when they enter and exit an element

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: NA

Examples:

• A screen reader might announce an inline link as something like "<name>, link"
• A screen reader might announce when it enter and exits a links the spans multiple lines.
• A screen reader might announce the link role for every line that the links spans

Expectation: provide shortcuts to jump to this role

Rationale:

Screen reader users might want to quickly navigate to elements of this type.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: SHOULD
• Voice Control: NA

Expectation: convey the visited state

Rationale:

A user might want to know that they have already visted the link

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MAY
• Voice Control: NA