Accessibility statement

WorldSkills accessibility statement is generated using the W3C Accessibility Statement Generator Tool.

The sample accessibility statement by GOV.UK was also useful.

 

Manual testing

Many organisations have created checklists to help identify potential accessibility issues affecting their websites or applications:

• 18F (the US government’s digital agency) checklist
• W3C Easy Checks
• Basic screen reader commands for accessibility testing
• WebAIM's WCAG 2 Checklist
• BBC Mobile Accessibility Guidelines

The tests covered:

• Semantic Structure and Navigation
• Images, Canvas, SVG, and Other Non-Text Content
• Visual Design and Colors
• Responsive Design and Zoom
• Form Labels, Instructions, and Validation

 

Automated testing and other tools

• Automated testing of main website layouts using Axe-core, an accessibility testing engine for websites and other HTML-based user interfaces.
• Manual testing of the main website layouts using tota11y, an accessibility visualization toolkit from Khan Academy.
• Color combination tested using the WCAG 2.0 guidelines for contrast accessibility

Keyboard accessibility

1. Test your site for keyboard accessibility

Not everyone uses a mouse to navigate websites. When navigating a website with a keyboard, the expected behaviours are:

Key	Expected functions	Notes
Tab (and shift + tab)	Navigate to interactive elements (forwards and backwards)	Check order of navigation makes sense. Check elements have focus indicator, i.e. it's clear the element is active.
Space	Activate a button Check/uncheck a checkbox Check/uncheck a radio button Expand a select (dropdown) menu Scroll up and down a page Start and stop video and audio	The space bar will, by default, scroll the page when input is not focused.
Enter	Activate a button Activate a link Expand the menu and select an option
Arrow up / down	Navigate between options in: Radio buttons Select menu Scroll up and down the page
Esc	Close dialogue box

 

• The space bar activates a link <a href>
• The space bar or the enter button activates a button <button>
• The WorldSkills pattern library buttons contains buttons which are marked up as links but visually look like buttons. In most cases, this approach works because they are links and should behave like links.