The hidden business of the internet mozilla

iOS: Does text adhere to the Dynamic Type Accessibility setting?.

Android: when you Zoom, does the text work as expected within the UI?.

Do errors or other information indicators get communicated with more than color? For example, instead of saying вЂњCorrect all fields marked in redвЂќ, provide contextual error messages everybody can relate to, including color-blind people (roughly 8% of the population).

Does text respect Bold text or Large Text, and other text-related accessibility settings?.

Is the text zoomable and/or flow in the interface as expected?.

Does the text (color) have enough contrast to the background so it conforms to WCAG 2.1 standards? For example, normal text must have a contrast ratio of 4.5:1 with its background to be valid.

Are form controls associated with a label for screen reader accessibility and bigger click targets for people who cannot accurately move the mouse or finger?ДЄpplies to markup languages and native user interfaces.

Is meaningful alternative text provided for images (or marked as decorative with an empty alt=вЂќвЂќ)?.

When a new screen, notification, or pop-up appears or is dismissed is the focus set appropriately? For example, when a pop-up appears, is focus moved to a control inside the pop-up? When a pop-up is dismissed, does focus return to the element which was focused before the pop-up appeared?.

Is the focus visible, even when a mouse is not used?.

Are custom widgets operable with the keyboard?.

Are custom widgets (containers like toolbars, dialogs, labelled groups, etc.), augmented with the proper WAI-ARIA roles, states and properties?.

If controls or content are visually hidden, are they also semantically hidden using the hidden attribute, CSS display: none, CSS visibility: hidden or aria-hidden?.

Are proper headings, lists, tables, etc.

Are buttons, checkboxes, links, list boxes, etc.

Is the markup semantic, wherever possible?.

This is not exhaustive and you will find more best practices and guidance in the detailed resources provided.ДЄll of the below can be checked with either the accessibility inspector in the Developer Tools toolbox and/or by navigating the user interface with a keyboard. When working in the following areas, we've provided a general list of considerations when designing, implementing, and testing accessibility.

To that end, this document outlines accessibility guidelines and resources which should be referenced before a Mozilla product or feature is considered release-ready. At Mozilla, accessibility is a fundamental part of our mission to ensure the internet is 'open and accessible to all,' helping to empower people, regardless of their abilities, to contribute to the common good.

The hidden business of the internet mozilla