Breadcrumbs test scenarios
These test scenarios are designed to be human readable by using Gherkin syntax. Almost all of them are automated behind the scenes using JavaScript and Playwright, which you can see in the GitHub repo.
Sections: the scenarios are grouped by the same themes as the accessibility requirements in the component documentation, so each section here matches a section there.
Tags: marked by an @ symbol, tags are a
way to group related tests. For example, by component name, whether
it's an automated or manual test, and the WCAG level and success
criterion number.
Steps: every scenario is written with the same shared set of Given, When and Then steps. See the full list of test steps for what each one does.
View accessibility requirements
Adaptability
View accessibility requirements: Adaptability
@breadcrumbs @adaptability Feature: Breadcrumbs — Adaptability Helping people by honouring user preferences and by allowing adaptations to content presentation and time limits User story: As a person who needs to adjust the way content is presented, or to adjust timings I want components that my tools can interpret and adjust so that I can navigate, understand, and operate the interface reliably using the technology that supports me. Background: Given I load the sample "http://localhost:8081/breadcrumbs/examples/default" # ---------------------------------------------------------------------------- # Perceivable # ---------------------------------------------------------------------------- @1.3.4 @aa @automatic Rule: 1.3.4 Orientation, Level AA Scenario Outline: Content is not restricted to a single orientation, unless it's essential When I switch to landscape mode And I view the rendered "<element>" Then it should not lose any content or functionality Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) | @1.4.4 @aa @automatic Rule: 1.4.4 Resize Text, Level AA Scenario Outline: Text can scale up to 200% without loss of content or functionality When I zoom in the browser to 200% And I view the rendered "<element>" Then it should not lose any content or functionality Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) | @1.4.10 @aa @automatic Rule: 1.4.10 Reflow, Level AA Scenario: Content reflows without horizontal scrolling at 320px wide When I view the rendered '.tl-breadcrumbs' And I set the viewport to 320px wide Then it should reflow without requiring horizontal scrolling @1.4.12 @aa @automatic Rule: 1.4.12 Text Spacing, Level AA Scenario: Line, letter and word spacing can be increased without a loss of content When I view the rendered '.tl-breadcrumbs' And I increase the line height to 1.5 times the font size And I increase the spacing following paragraphs to 2 times the font size And I increase the letter spacing to 0.12 times the font size And I increase the word spacing to 0.16 times the font size Then it should not lose any content or functionality @recommendation @automatic Rule: Recommendation Scenario: Content and information remains visible and understandable when using high contrast themes When I enable "forced colors" mode And I view the rendered '.tl-breadcrumbs' Then it should not lose any content or functionalityFeature: Breadcrumbs — Adaptability
Helping people by honouring user preferences and by allowing adaptations to content presentation and time limits
User story:
As a person who needs to adjust the way content is presented, or to adjust timings I want components that my tools can interpret and adjust so that I can navigate, understand, and operate the interface reliably using the technology that supports me.
Background:
Given I load the sample "https://tetralogical.com/resources/accessible-components-library/breadcrumbs/examples/default.html"
1.3.4 Orientation
Rule: 1.3.4 Orientation, Level AA
Scenario Outline: Content is not restricted to a single orientation, unless it's essential
When I switch to landscape mode
And I view the rendered "<element>"
Then it should not lose any content or functionality
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
1.4.4 Resize Text
Rule: 1.4.4 Resize Text, Level AA
Scenario Outline: Text can scale up to 200% without loss of content or functionality
When I zoom in the browser to 200%
And I view the rendered "<element>"
Then it should not lose any content or functionality
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
1.4.10 Reflow
Rule: 1.4.10 Reflow, Level AA
Scenario: Content reflows without horizontal scrolling at 320px wide
When I view the rendered '.tl-breadcrumbs'
And I set the viewport to 320px wide
Then it should reflow without requiring horizontal scrolling
1.4.12 Text Spacing
Rule: 1.4.12 Text Spacing, Level AA
Scenario: Line, letter and word spacing can be increased without a loss of content
When I view the rendered '.tl-breadcrumbs'
And I increase the line height to 1.5 times the font size
And I increase the spacing following paragraphs to 2 times the font size
And I increase the letter spacing to 0.12 times the font size
And I increase the word spacing to 0.16 times the font size
Then it should not lose any content or functionality
Recommendations
Rule: Recommendation
Scenario: Content and information remains visible and understandable when using high contrast themes
When I enable "forced colors" mode
And I view the rendered '.tl-breadcrumbs'
Then it should not lose any content or functionality
Animation and movement
View accessibility requirements: Animation and movement
@breadcrumbs @animation-and-movement Feature: Breadcrumbs — Animation and movement Helping people to limit animation or reduce motion within content No component-specific requirementsFeature: Breadcrumbs — Animation and movement
Helping people to limit animation or reduce motion within content
No component-specific requirements
Assistive technologies and semantics
View accessibility requirements: Assistive technologies and semantics
@breadcrumbs @assistive-technologies-and-semantics Feature: Breadcrumbs — Assistive technologies and semantics Helping people who use a screen reader or other assistive tech by using appropriate code User story: As a person who uses assistive technology I want components that use semantic markup, roles, and states that my tools can interpret so that I can navigate, understand, and operate the interface reliably. Background: Given I load the sample "http://localhost:8081/breadcrumbs/examples/default" # ---------------------------------------------------------------------------- # Perceivable # ---------------------------------------------------------------------------- @1.3.1 @a @automatic Rule: 1.3.1 Info and Relationships, Level A Scenario Outline: If text characters are used as visual separators between breadcrumb items to indicate hierarchy, they are not conveyed to screen readers When I inspect "<element>" in the Accessibility Tree And it has the pseudo element "::before" Then its accessible name and visible text should be identical Examples: | element | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a | @1.3.1 @a @automatic Rule: 1.3.1 Info and Relationships, Level A Scenario: If the last item in the breadcrumbs represents the current page and is visually different, the aria-current attribute is used to programmatically identify it When I inspect ".tl-breadcrumbs li:nth-child(3) a" in the DOM Then it should have the attribute "aria-current" with the value "page" @1.3.2 @a @automatic Rule: 1.3.2 Meaningful Sequence, Level A Scenario Outline: The order of content in the HTML matches the reading order When I inspect "<element>" in the DOM Then it is positioned after the "<previous_element>" element in the DOM Examples: | element | previous_element | | .tl-breadcrumbs li:nth-child(2) a | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(3) a | .tl-breadcrumbs li:nth-child(2) a | @2.5.3 @a @automatic Rule: 2.5.3 Label in Name, Level A Scenario Outline: Each link has an accessible name that matches or includes the visible label When I view the rendered "<element>" Then it should have an accessible name which contains the visible label "<visible_label>" Examples: | element | visible_label | | .tl-breadcrumbs li:nth-child(1) a | Home | | .tl-breadcrumbs li:nth-child(2) a | About | | .tl-breadcrumbs li:nth-child(3) a | Team | @4.1.2 @a @automatic Rule: 4.1.2 Name, Role, Value, Level A Scenario Outline: Each link has an accessible name When I inspect "<element>" in the DOM Then it should have an accessible name And its accessible name should be "<name>" Examples: | element | name | | .tl-breadcrumbs li:nth-child(1) a | Home | | .tl-breadcrumbs li:nth-child(2) a | About | | .tl-breadcrumbs li:nth-child(3) a | Team | @4.1.2 @a @automatic Rule: 4.1.2 Name, Role, Value, Level A Scenario Outline: Each link has the correct accessible role When I inspect "<element>" in the DOM Then it should have an accessible role of "<role>" Examples: | element | role | | .tl-breadcrumbs li:nth-child(1) a | link | | .tl-breadcrumbs li:nth-child(2) a | link | | .tl-breadcrumbs li:nth-child(3) a | link | @4.1.2 @a @automatic Rule: 4.1.2 Name, Role, Value, Level A Scenario: A navigation landmark is used to identify a navigation region When I inspect ".tl-breadcrumbs" in the DOM Then it should have an accessible role of "navigation" @recommendation @automatic Rule: Recommendation Scenario: Markup can be parsed without errors When I inspect ".tl-breadcrumbs" in the DOM Then it should use valid HTML with no parsing errors @recommendation @automatic Rule: Recommendation Scenario Outline: Each link is implemented as an <a> element with an href attribute When I inspect "<element>" in the DOM Then it should use the tag "a" And it should have the attribute "<attribute>" with the value "<value>" Examples: | element | attribute | value | | .tl-breadcrumbs li:nth-child(1) a | href | / | | .tl-breadcrumbs li:nth-child(2) a | href | /about | | .tl-breadcrumbs li:nth-child(3) a | href | /about/team | @recommendation @automatic Rule: Recommendation Scenario Outline: An ordered list is used to provide structure for the breadcrumb items When I inspect "<element>" in the DOM Then it should use the tag "<tag>" Examples: | element | tag | | .tl-breadcrumbs > ol | ol | | .tl-breadcrumbs ol li:nth-child(1) | li | | .tl-breadcrumbs ol li:nth-child(2) | li | | .tl-breadcrumbs ol li:nth-child(3) | li | @recommendation @automatic Rule: Recommendation Scenario: The navigation landmark has a descriptive accessible name such as "Breadcrumb" When I inspect ".tl-breadcrumbs" in the DOM Then it should have an accessible name And its accessible name should be "Breadcrumb"Feature: Breadcrumbs — Assistive technologies and semantics
Helping people who use a screen reader or other assistive tech by using appropriate code
User story:
As a person who uses assistive technology I want components that use semantic markup, roles, and states that my tools can interpret so that I can navigate, understand, and operate the interface reliably.
Background:
Given I load the sample "https://tetralogical.com/resources/accessible-components-library/breadcrumbs/examples/default.html"
1.3.1 Info and Relationships
Rule: 1.3.1 Info and Relationships, Level A
Scenario Outline: If text characters are used as visual separators between breadcrumb items to indicate hierarchy, they are not conveyed to screen readers
When I inspect "<element>" in the Accessibility Tree
And it has the pseudo element "::before"
Then its accessible name and visible text should be identical
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
Rule: 1.3.1 Info and Relationships, Level A
Scenario: If the last item in the breadcrumbs represents the current page and is visually different, the aria-current attribute is used to programmatically identify it
When I inspect ".tl-breadcrumbs li:nth-child(3) a" in the DOM
Then it should have the attribute "aria-current" with the value "page"
1.3.2 Meaningful Sequence
Rule: 1.3.2 Meaningful Sequence, Level A
Scenario Outline: The order of content in the HTML matches the reading order
When I inspect "<element>" in the DOM
Then it is positioned after the "<previous_element>" element in the DOM
Examples:
| element | previous_element |
|---|---|
| .tl-breadcrumbs li:nth-child(2) a | .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(3) a | .tl-breadcrumbs li:nth-child(2) a |
2.5.3 Label in Name
Rule: 2.5.3 Label in Name, Level A
Scenario Outline: Each link has an accessible name that matches or includes the visible label
When I view the rendered "<element>"
Then it should have an accessible name which contains the visible label "<visible_label>"
Examples:
| element | visible_label |
|---|---|
| .tl-breadcrumbs li:nth-child(1) a | Home |
| .tl-breadcrumbs li:nth-child(2) a | About |
| .tl-breadcrumbs li:nth-child(3) a | Team |
4.1.2 Name, Role, Value
Rule: 4.1.2 Name, Role, Value, Level A
Scenario Outline: Each link has an accessible name
When I inspect "<element>" in the DOM
Then it should have an accessible name
And its accessible name should be "<name>"
Examples:
| element | name |
|---|---|
| .tl-breadcrumbs li:nth-child(1) a | Home |
| .tl-breadcrumbs li:nth-child(2) a | About |
| .tl-breadcrumbs li:nth-child(3) a | Team |
Rule: 4.1.2 Name, Role, Value, Level A
Scenario Outline: Each link has the correct accessible role
When I inspect "<element>" in the DOM
Then it should have an accessible role of "<role>"
Examples:
| element | role |
|---|---|
| .tl-breadcrumbs li:nth-child(1) a | link |
| .tl-breadcrumbs li:nth-child(2) a | link |
| .tl-breadcrumbs li:nth-child(3) a | link |
Rule: 4.1.2 Name, Role, Value, Level A
Scenario: A navigation landmark is used to identify a navigation region
When I inspect ".tl-breadcrumbs" in the DOM
Then it should have an accessible role of "navigation"
Recommendations
Rule: Recommendation
Scenario: Markup can be parsed without errors
When I inspect ".tl-breadcrumbs" in the DOM
Then it should use valid HTML with no parsing errors
Rule: Recommendation
Scenario Outline: Each link is implemented as an <a> element with an href attribute
When I inspect "<element>" in the DOM
Then it should use the tag "a"
And it should have the attribute "<attribute>" with the value "<value>"
Examples:
| element | attribute | value |
|---|---|---|
| .tl-breadcrumbs li:nth-child(1) a | href | / |
| .tl-breadcrumbs li:nth-child(2) a | href | /about |
| .tl-breadcrumbs li:nth-child(3) a | href | /about/team |
Rule: Recommendation
Scenario Outline: An ordered list is used to provide structure for the breadcrumb items
When I inspect "<element>" in the DOM
Then it should use the tag "<tag>"
Examples:
| element | tag |
|---|---|
| .tl-breadcrumbs > ol | ol |
| .tl-breadcrumbs ol li:nth-child(1) | li |
| .tl-breadcrumbs ol li:nth-child(2) | li |
| .tl-breadcrumbs ol li:nth-child(3) | li |
Rule: Recommendation
Scenario: The navigation landmark has a descriptive accessible name such as "Breadcrumb"
When I inspect ".tl-breadcrumbs" in the DOM
Then it should have an accessible name
And its accessible name should be "Breadcrumb"
Colour and contrast
View accessibility requirements: Colour and contrast
@breadcrumbs @colour-and-contrast Feature: Breadcrumbs — Colour and contrast Helping people who struggle with colour perception or low vision User story: As a person with low vision or colour vision deficiency I want components with sufficient contrast and that don't rely solely on colour so that I can perceive and understand all content and interface elements. Background: Given I load the sample "http://localhost:8081/breadcrumbs/examples/default" # ---------------------------------------------------------------------------- # Perceivable # ---------------------------------------------------------------------------- @1.4.1 @a @automatic Rule: 1.4.1 Use of Color, Level A Scenario Outline: Links are identifiable without relying on colour alone When I view the rendered "<element>" Then it should be visually identifiable as a link without relying on colour alone Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a | Scenario: The current page is distinguishable from the other links without relying on colour alone When I view the rendered ".tl-breadcrumbs li:nth-child(3) a" Then it should be distinguishable from ".tl-breadcrumbs li:nth-child(1) a" without relying on colour alone @1.4.3 @aa @automatic Rule: 1.4.3 Contrast (Minimum), Level AA Scenario Outline: Each link has a contrast ratio of 4.5:1 against the background When I view the rendered "<element>" Then its text should have a contrast ratio of '4.5:1' against its background Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a | @1.4.3 @aa @automatic @darkmode Rule: 1.4.3 Contrast (Minimum), Level AA Scenario Outline: Darkmode: Each link has a contrast ratio of 4.5:1 against the background When I view the rendered "<element>" And I enable "dark" mode Then its text should have a contrast ratio of '4.5:1' against its background Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a | @1.4.11 @aa @automatic Rule: 1.4.11 Non-text Contrast, Level AA Scenario Outline: Visual separators between breadcrumb items have a minimum contrast ratio of 3:1 against the background When I view the rendered "<element>" And it has the pseudo element "::before" Then its pseudo element should have a contrast ratio of '3:1' against its background Examples: | element | | .tl-breadcrumbs li:nth-child(2) div | | .tl-breadcrumbs li:nth-child(3) div | @1.4.11 @aa @automatic @darkmode Rule: 1.4.11 Non-text Contrast, Level AA Scenario Outline: Darkmode: Visual separators between breadcrumb items have a minimum contrast ratio of 3:1 against the background When I view the rendered "<element>" And I enable "dark" mode And it has the pseudo element "::before" Then its pseudo element should have a contrast ratio of '3:1' against its background Examples: | element | | .tl-breadcrumbs li:nth-child(2) div | | .tl-breadcrumbs li:nth-child(3) div | @1.4.6 @aaa @automatic Rule: 1.4.6 Contrast (Enhanced), Level AAA Scenario Outline: Each link has a contrast ratio of least 7:1 When I view the rendered "<element>" Then its text should have a contrast ratio of '7:1' against its background Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a | @1.4.6 @aaa @automatic @darkmode Rule: 1.4.6 Contrast (Enhanced), Level AAA Scenario Outline: Darkmode: Each link has a contrast ratio of 7:1 When I view the rendered "<element>" And I enable "dark" mode Then its text should have a contrast ratio of '7:1' against its background Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a |Feature: Breadcrumbs — Colour and contrast
Helping people who struggle with colour perception or low vision
User story:
As a person with low vision or colour vision deficiency I want components with sufficient contrast and that don't rely solely on colour so that I can perceive and understand all content and interface elements.
Background:
Given I load the sample "https://tetralogical.com/resources/accessible-components-library/breadcrumbs/examples/default.html"
1.4.1 Use of Color
Rule: 1.4.1 Use of Color, Level A
Scenario Outline: Links are identifiable without relying on colour alone
When I view the rendered "<element>"
Then it should be visually identifiable as a link without relying on colour alone
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
Scenario: The current page is distinguishable from the other links without relying on colour alone
When I view the rendered ".tl-breadcrumbs li:nth-child(3) a"
Then it should be distinguishable from ".tl-breadcrumbs li:nth-child(1) a" without relying on colour alone
1.4.3 Contrast (Minimum)
Rule: 1.4.3 Contrast (Minimum), Level AA
Scenario Outline: Each link has a contrast ratio of 4.5:1 against the background
When I view the rendered "<element>"
Then its text should have a contrast ratio of '4.5:1' against its background
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
Rule: 1.4.3 Contrast (Minimum), Level AA
Scenario Outline: Darkmode: Each link has a contrast ratio of 4.5:1 against the background
When I view the rendered "<element>"
And I enable "dark" mode
Then its text should have a contrast ratio of '4.5:1' against its background
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
1.4.11 Non-text Contrast
Rule: 1.4.11 Non-text Contrast, Level AA
Scenario Outline: Visual separators between breadcrumb items have a minimum contrast ratio of 3:1 against the background
When I view the rendered "<element>"
And it has the pseudo element "::before"
Then its pseudo element should have a contrast ratio of '3:1' against its background
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(2) div |
| .tl-breadcrumbs li:nth-child(3) div |
Rule: 1.4.11 Non-text Contrast, Level AA
Scenario Outline: Darkmode: Visual separators between breadcrumb items have a minimum contrast ratio of 3:1 against the background
When I view the rendered "<element>"
And I enable "dark" mode
And it has the pseudo element "::before"
Then its pseudo element should have a contrast ratio of '3:1' against its background
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(2) div |
| .tl-breadcrumbs li:nth-child(3) div |
1.4.6 Contrast (Enhanced)
Rule: 1.4.6 Contrast (Enhanced), Level AAA
Scenario Outline: Each link has a contrast ratio of least 7:1
When I view the rendered "<element>"
Then its text should have a contrast ratio of '7:1' against its background
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
Rule: 1.4.6 Contrast (Enhanced), Level AAA
Scenario Outline: Darkmode: Each link has a contrast ratio of 7:1
When I view the rendered "<element>"
And I enable "dark" mode
Then its text should have a contrast ratio of '7:1' against its background
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
Consistency and predictability
View accessibility requirements: Consistency and predictability
@breadcrumbs @consistency-and-predictability Feature: Breadcrumbs — Consistency and predictability Helping people by keeping functionality consistent and predictable User story: As a person who benefits from consistent and predictable interfaces I want components that behave in expected ways and don't cause unexpected changes so that I can navigate and interact with confidence. Background: Given I load the sample "http://localhost:8081/breadcrumbs/examples/default" # ---------------------------------------------------------------------------- # Understandable # ---------------------------------------------------------------------------- @3.2.1 @a @automatic Rule: 3.2.1 On Focus, Level A Scenario Outline: Receiving focus does not initiate a change of context When I focus "<element>" using a keyboard Then it should NOT navigate to a new page Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a | @3.2.3 @aa @automatic Rule: 3.2.3 Consistent Navigation, Level AA Scenario: The location of the breadcrumbs component is consistent on multiple pages When I inspect '.tl-breadcrumbs' in the DOM Then it is positioned after the 'body' element in the DOM @3.2.4 @aa @automatic Rule: 3.2.4 Consistent Identification, Level AA Scenario: The breadcrumbs component is identified consistently on multiple pages When I inspect '.tl-breadcrumbs' in the DOM Then its accessible name should be 'Breadcrumb'Feature: Breadcrumbs — Consistency and predictability
Helping people by keeping functionality consistent and predictable
User story:
As a person who benefits from consistent and predictable interfaces I want components that behave in expected ways and don't cause unexpected changes so that I can navigate and interact with confidence.
Background:
Given I load the sample "https://tetralogical.com/resources/accessible-components-library/breadcrumbs/examples/default.html"
3.2.1 On Focus
Rule: 3.2.1 On Focus, Level A
Scenario Outline: Receiving focus does not initiate a change of context
When I focus "<element>" using a keyboard
Then it should NOT navigate to a new page
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
3.2.3 Consistent Navigation
Rule: 3.2.3 Consistent Navigation, Level AA
Scenario: The location of the breadcrumbs component is consistent on multiple pages
When I inspect '.tl-breadcrumbs' in the DOM
Then it is positioned after the 'body' element in the DOM
3.2.4 Consistent Identification
Rule: 3.2.4 Consistent Identification, Level AA
Scenario: The breadcrumbs component is identified consistently on multiple pages
When I inspect '.tl-breadcrumbs' in the DOM
Then its accessible name should be 'Breadcrumb'
Images and media
View accessibility requirements: Images and media
@breadcrumbs @images-and-media Feature: Breadcrumbs — Images and media Helping people to access (and remove distractions caused by) image, video and audio content User story: As a person who cannot see images I want appropriate text alternatives for images so that I can access the same information as everyone else. Background: Given I load the sample "http://localhost:8081/breadcrumbs/examples/default" # ---------------------------------------------------------------------------- # Perceivable # ---------------------------------------------------------------------------- @1.4.5 @aa @automatic Rule: 1.4.5 Images of Text, Level AA Scenario: Real text is used instead of images of text (except essential/logos) When I view the rendered '.tl-breadcrumbs' Then it should not contain any images @1.4.9 @aaa @automatic Rule: 1.4.9 Images of Text (No Exception), Level AAA Scenario: No images of text at all When I view the rendered '.tl-breadcrumbs' Then it should not contain any imagesFeature: Breadcrumbs — Images and media
Helping people to access (and remove distractions caused by) image, video and audio content
User story:
As a person who cannot see images I want appropriate text alternatives for images so that I can access the same information as everyone else.
Background:
Given I load the sample "https://tetralogical.com/resources/accessible-components-library/breadcrumbs/examples/default.html"
1.4.5 Images of Text
Rule: 1.4.5 Images of Text, Level AA
Scenario: Real text is used instead of images of text (except essential/logos)
When I view the rendered '.tl-breadcrumbs'
Then it should not contain any images
1.4.9 Images of Text (No Exception)
Rule: 1.4.9 Images of Text (No Exception), Level AAA
Scenario: No images of text at all
When I view the rendered '.tl-breadcrumbs'
Then it should not contain any images
Input assistance
View accessibility requirements: Input assistance
@breadcrumbs @input-assistance Feature: Breadcrumbs — Input assistance Helping people to complete forms, enter data and pass authentication No component-specific requirementsFeature: Breadcrumbs — Input assistance
Helping people to complete forms, enter data and pass authentication
No component-specific requirements
Keyboard
View accessibility requirements: Keyboard
@breadcrumbs @keyboard Feature: Breadcrumbs — Keyboard Helping people who use a keyboard User story: As a keyboard user I want components that follow a logical tab order and provide visible, predictable focus states so that I can move through the interface efficiently and operate every feature without using a mouse. Background: Given I load the sample "http://localhost:8081/breadcrumbs/examples/default" # ---------------------------------------------------------------------------- # Operable # ---------------------------------------------------------------------------- @2.1.1 @a @automatic Rule: 2.1.1 Keyboard, Level A Scenario Outline: Each link is focusable using the Tab key When I focus "<element>" And I press the 'TAB' key once Then "<next element>" should be focused Examples: | element | next element | | .tl-breadcrumbs li:nth-child(1) a | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(2) a | .tl-breadcrumbs li:nth-child(3) a | @2.1.1 @a @automatic Rule: 2.1.1 Keyboard, Level A Scenario Outline: Each link is clickable using the Enter key When I focus "<element>" And I press the 'ENTER' key once Then it should navigate to a new page Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a | @2.1.2 @a @automatic Rule: 2.1.2 No Keyboard Trap, Level A Scenario: Each link does not trap focus going forwards When I focus '.tl-breadcrumbs li:last-child a' And I press the 'TAB' key once Then the focus should not be on a '.tl-breadcrumbs a' element @2.1.2 @a @automatic Rule: 2.1.2 No Keyboard Trap, Level A Scenario: Each link does not trap focus going backwards When I focus '.tl-breadcrumbs li:first-child a' And I hold the 'SHIFT' key And I press the 'TAB' key once Then the focus should not be on a '.tl-breadcrumbs a' element @2.4.3 @a @automatic Rule: 2.4.3 Focus Order, Level A Scenario Outline: Each link receives focus in logical order When I focus "<element>" And I press the 'TAB' key once Then "<next element>" should be focused Examples: | element | next element | | .tl-breadcrumbs li:nth-child(1) a | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(2) a | .tl-breadcrumbs li:nth-child(3) a | @2.4.7 @aa @automatic Rule: 2.4.7 Focus Visible, Level AA Scenario Outline: Keyboard focus indicator is visible and discernible When I focus "<element>" using a keyboard Then it should have a visible focus indicator Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) | @2.4.11 @aa @automatic Rule: 2.4.11 Focus Not Obscured (Minimum), Level AA Scenario Outline: Each link is not fully hidden by other content when it receives keyboard focus When I focus "<element>" using a keyboard Then it should have a visible focus indicator And its focus indicator should be at least partially visible Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) | @2.4.12 @aaa @automatic Rule: 2.4.12 Focus Not Obscured (Enhanced), Level AAA Scenario Outline: Focus is not even partially hidden by other content When I focus "<element>" using a keyboard Then it should have a visible focus indicator And its focus indicator should be fully visible Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) | @2.4.13 @aaa @automatic Rule: 2.4.13 Focus Appearance, Level AAA Scenario Outline: Each link has a custom focus style with a solid 2 pixel thick perimeter, or equivalent, and a contrast ratio of at least 3:1 against the background colour When I focus "<element>" using a keyboard Then it should have a visible focus indicator And the focus indicator should have a contrast ratio of 3:1 against its background And its focus indicator should have a minimum perimiter thickness of 2px Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) |Feature: Breadcrumbs — Keyboard
Helping people who use a keyboard
User story:
As a keyboard user I want components that follow a logical tab order and provide visible, predictable focus states so that I can move through the interface efficiently and operate every feature without using a mouse.
Background:
Given I load the sample "https://tetralogical.com/resources/accessible-components-library/breadcrumbs/examples/default.html"
2.1.1 Keyboard
Rule: 2.1.1 Keyboard, Level A
Scenario Outline: Each link is focusable using the Tab key
When I focus "<element>"
And I press the 'TAB' key once
Then "<next element>" should be focused
Examples:
| element | next element |
|---|---|
| .tl-breadcrumbs li:nth-child(1) a | .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(2) a | .tl-breadcrumbs li:nth-child(3) a |
Rule: 2.1.1 Keyboard, Level A
Scenario Outline: Each link is clickable using the Enter key
When I focus "<element>"
And I press the 'ENTER' key once
Then it should navigate to a new page
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |
2.1.2 No Keyboard Trap
Rule: 2.1.2 No Keyboard Trap, Level A
Scenario: Each link does not trap focus going forwards
When I focus '.tl-breadcrumbs li:last-child a'
And I press the 'TAB' key once
Then the focus should not be on a '.tl-breadcrumbs a' element
Rule: 2.1.2 No Keyboard Trap, Level A
Scenario: Each link does not trap focus going backwards
When I focus '.tl-breadcrumbs li:first-child a'
And I hold the 'SHIFT' key
And I press the 'TAB' key once
Then the focus should not be on a '.tl-breadcrumbs a' element
2.4.3 Focus Order
Rule: 2.4.3 Focus Order, Level A
Scenario Outline: Each link receives focus in logical order
When I focus "<element>"
And I press the 'TAB' key once
Then "<next element>" should be focused
Examples:
| element | next element |
|---|---|
| .tl-breadcrumbs li:nth-child(1) a | .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(2) a | .tl-breadcrumbs li:nth-child(3) a |
2.4.7 Focus Visible
Rule: 2.4.7 Focus Visible, Level AA
Scenario Outline: Keyboard focus indicator is visible and discernible
When I focus "<element>" using a keyboard
Then it should have a visible focus indicator
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
2.4.11 Focus Not Obscured (Minimum)
Rule: 2.4.11 Focus Not Obscured (Minimum), Level AA
Scenario Outline: Each link is not fully hidden by other content when it receives keyboard focus
When I focus "<element>" using a keyboard
Then it should have a visible focus indicator
And its focus indicator should be at least partially visible
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
2.4.12 Focus Not Obscured (Enhanced)
Rule: 2.4.12 Focus Not Obscured (Enhanced), Level AAA
Scenario Outline: Focus is not even partially hidden by other content
When I focus "<element>" using a keyboard
Then it should have a visible focus indicator
And its focus indicator should be fully visible
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
2.4.13 Focus Appearance
Rule: 2.4.13 Focus Appearance, Level AAA
Scenario Outline: Each link has a custom focus style with a solid 2 pixel thick perimeter, or equivalent, and a contrast ratio of at least 3:1 against the background colour
When I focus "<element>" using a keyboard
Then it should have a visible focus indicator
And the focus indicator should have a contrast ratio of 3:1 against its background
And its focus indicator should have a minimum perimiter thickness of 2px
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
Pointer and touch
View accessibility requirements: Pointer and touch
@breadcrumbs @pointer-and-touch Feature: Breadcrumbs — Pointer and touch Helping people use single pointer or touch interactions User story: As a person using touch or pointer input I want components with accessible gestures, adequate target sizes, and predictable interactions so that I can accurately interact with all functionality. Background: Given I load the sample "http://localhost:8081/breadcrumbs/examples/default" # ---------------------------------------------------------------------------- # Operable # ---------------------------------------------------------------------------- @2.5.2 @a @automatic Rule: 2.5.2 Pointer Cancellation, Level A Scenario: Each link is activated on the up event, not on the down event When I press the mouse down on "<element>" Then it should NOT navigate to a new page Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) | @2.5.8 @aa @automatic Rule: 2.5.8 Target Size (Minimum), Level AA Scenario Outline: Each link has a target area size and spacing of at least 24 by 24 pixels When I view the rendered "<element>" Then it should have a width and height of at least 24px Examples: | element | | .tl-breadcrumbs li:nth-child(1) | | .tl-breadcrumbs li:nth-child(2) | | .tl-breadcrumbs li:nth-child(3) | @2.5.5 @aaa @automatic Rule: 2.5.5 Target Size (Enhanced), Level AAA Scenario Outline: Each link has a target area size and spacing of at least 44 by 44 pixels When I view the rendered "<element>" Then it should have a width and height of at least 44px Examples: | element | | .tl-breadcrumbs li:nth-child(1) a | | .tl-breadcrumbs li:nth-child(2) a | | .tl-breadcrumbs li:nth-child(3) a |Feature: Breadcrumbs — Pointer and touch
Helping people use single pointer or touch interactions
User story:
As a person using touch or pointer input I want components with accessible gestures, adequate target sizes, and predictable interactions so that I can accurately interact with all functionality.
Background:
Given I load the sample "https://tetralogical.com/resources/accessible-components-library/breadcrumbs/examples/default.html"
2.5.2 Pointer Cancellation
Rule: 2.5.2 Pointer Cancellation, Level A
Scenario: Each link is activated on the up event, not on the down event
When I press the mouse down on "<element>"
Then it should NOT navigate to a new page
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
2.5.8 Target Size (Minimum)
Rule: 2.5.8 Target Size (Minimum), Level AA
Scenario Outline: Each link has a target area size and spacing of at least 24 by 24 pixels
When I view the rendered "<element>"
Then it should have a width and height of at least 24px
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) |
| .tl-breadcrumbs li:nth-child(2) |
| .tl-breadcrumbs li:nth-child(3) |
2.5.5 Target Size (Enhanced)
Rule: 2.5.5 Target Size (Enhanced), Level AAA
Scenario Outline: Each link has a target area size and spacing of at least 44 by 44 pixels
When I view the rendered "<element>"
Then it should have a width and height of at least 44px
Examples:
| element |
|---|
| .tl-breadcrumbs li:nth-child(1) a |
| .tl-breadcrumbs li:nth-child(2) a |
| .tl-breadcrumbs li:nth-child(3) a |