Birmingham Digital Resource Accessibility Audit

Birmingham Digital Resource Accessibility Audit
Instructions: All City of Birmingham web content and mobile apps must meet WCAG Level 2.1 AA standards. Use both automated and manual checks; recommended tools: MAUVE++ or ObservePoint.

You will be required to submit proof of compliance or non-compliance at the end of this form, including:
- Automated test results
- WCAG violations (cite criterion numbers)
- Proposed remediation solution and timeline
- Non-compliant resources may be disabled until corrected.
You can save your progress and return to this form later by using the "save" button at the bottom of the page.
Full Name*

First NameLast Name
Email Address*
example@example.com
Contact Number*
Please enter a valid phone number.Format: (000) 000-0000.
WebsiteMobile App
I am the developerI am a vendorI am a digital resource administratorOther/Unsure
What is the URL of the website that you are submitting for?*
e.g. https://www.birminghamal.gov
What is the name of the mobile app that you are submitting for?*
e.g. My BHAM 311
Who is your primary contact for this resource at the City of Birmingham?*
example@example.com
For Your Reference: Review Success Criteria For Each Item

1. Perceivable

Information and user interface components must be presentable to users in ways they can perceive.
1.1 Text Alternatives

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 (A) All images and non-text content that conveys necessary meaning or information needs a text alternative (alt text).*
Non-text Content
1.2 Time-based Media

If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content.
1.2.1 (A) All video-only and audio-only content has a text transcript. Transcripts are clearly labeled and available near the media.*
Audio-only and Video-only (Prerecorded)
1.2.2 (A) All video with sound has closed captioning.*
Captions (Prerecorded)
1.2.3 (A) For any video where meaningful information is not available audibly, a transcript or an audio description describing that information has been added.*
Audio Description or Media Alternative
1.2.4 (AA) Captions are provided for all live audio content in synchronized media.*
Captions (Live)
1.2.5 (AA) Audio description is provided for all prerecorded video content in synchronized media.*
Audio Description (Prerecorded)
1.3 Adaptable

Content that can be presented in different ways (for example: simpler layout) without losing information or structure
1.3.1 (A) Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.*
Info and Relationships
1.3.2 (A) When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.*
Meaningful Sequences
1.3.3 (A) Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.*
Sensory Characteristics
1.3.4 (AA) Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.*
Orientation
1.3.5 (AA) The purpose of an input element can be determined so browsers and assistive technology can help guide and facilitate inputting information.*
Identify Input Purposes
1.4 Distinguishable

Ease at which users see and hear content
1.4.1 (A) Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.*
Use of Color
1.4.2 (A) If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.*
Audio Control
1.4.3 (AA) Color contrast ratio of at least 4.5:1 between regular text and background; 3:1 for large text.*
Contrast (Minimum)
1.4.4 (AA) Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.*
Resize Text
1.4.5 (AA) Does not use images of text unless essential (e.g., logo).*
Images of Text
1.4.10 (AA) Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels.*
Reflow
1.4.11 (AA) All meaningful non-text content (buttons, form fields, icons) should have minimum 3:1 color contrast ratio.We might *
Non-text Contrast
1.4.12 (AA) In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size.*
Text Spacing
1.4.13 (AA) When pointer hover or keyboard focus makes additional content appear and then disappear, all of the following must be true: Dismissible: Users can dismiss the additional content without moving hover or focus, unless it shows an input error or does not obscure/replace other content. Hoverable: If hover triggers the content, users can move the pointer over it without it disappearing. Persistent: The content stays visible until the hover/focus trigger is removed, the user dismisses it, or the information becomes invalid.*
Content on Hover of Focus

2. Operable

User interface components and navigation must be operable.
2.1 Keyboard Accessible

All functionality available from a keyboard
2.1.1 (A) All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints*
Keyboard
2.1.2 (A) If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.*
No Keyboard Trap
2.1.4 (A) If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: A mechanism is available to turn the shortcut off; A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt); The keyboard shortcut for a user interface component is only active when that component has focus.*
Character Key Shortcuts
2.2 Enough Time

Users are provided enough time to read and use content.
2.2.1 (A) For each time limit that is set by the content, at least one of the following is true: The user is allowed to turn off the time limit before encountering it; The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or The time limit is essential and extending it would invalidate the activity; or The time limit is longer than 20 hours.*
Timing Adjustable
2.2.2 (A) For moving, blinking, scrolling, or auto-updating information, all of the following are true: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.*
Pause, Stop, Hide
2.3 Seizures and Physical Reactions

Content is not designed in a way that is known to cause seizures or physical reactions.
2.3.1 (A) Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.*
Three Flashes or Below Threshold
2.4 Navigable

Users are provided ways to navigate, find content, and determine where they are.
2.4.1 (A) A mechanism is available to bypass blocks of content that are repeated on multiple web pages.*
Bypass Blocks
2.4.2 (A) Web pages have titles that describe topic or purpose.*
Page Titled
2.4.3 (A) If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.*
Focus Order
2.4.4 (A) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.*
Link Purpose (In Context)
2.4.5 (AA) More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process.*
Multiple Ways
2.4.6 (AA) Headings and labels describe topic or purpose.*
Headings and Labels
2.4.7 (AA) Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.*
Focus Visible
2.4.11 (AA) When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.*
Focus Not Obscured (Minimum)
2.5 Input Modalities

Users are able to more easily operate functionality through various inputs beyond keyboard.
2.5.1 (A) All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.*
Pointer Gestures
2.5.2 (A) For functionality that can be operated using a single pointer, at least one of the following is true: The down-event of the pointer is not used to execute any part of the function; Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; The up-event reverses any outcome of the preceding down-event; Completing the function on the down-event is essential.*
Pointer Cancellation
2.5.3 (A) For user interface components with labels that include text or images of text, the name contains the text that is presented visually.*
Label in Name
2.5.4 (A) Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: The motion is used to operate functionality through an accessibility supported interface; The motion is essential for the function and doing so would invalidate the activity.*
Motion Actuation
2.5.7 (AA) All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.*
Dragging Movements
2.5.8 (AA) The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target; The function can be achieved through a different control on the same page that meets this criterion; The target is in a sentence or its size is otherwise constrained by the line-height of non-target text; The size of the target is determined by the user agent and is not modified by the author; A particular presentation of the target is essential or is legally required for the information being conveyed.*
Target Size (Minimum)

3. Understandable

The website and its user interface components must be presented in and operate in an understandable and predictable way.
3.1 Readable

Text content should be readable and understandable.
3.1.1 (A) The default human language of each web page can be programmatically determined. *
Language of Page
3.1.2 (AA) The human language of each passage in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.*
Language of Parts
3.2 Predictable

Web pages appear and operate in predictable ways.
3.2.1 (A) When any user interface component receives focus, it does not initiate a change of context.*
On Focus
3.2.2 (A) Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.*
On Input
3.2.3 (AA) Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.*
Consistent Navigation
3.2.4 (AA) Components that have the same functionality within a set of web pages are identified consistently.*
Consistent Identification
3.2.6 (A) If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they should occur in the same order relative to other page content, unless a change is initiated by the user: Human contact details; Human contact mechanism; Self-help option; A fully automated contact mechanism.*
Consistent Help
3.3 Input Assistance

Help users avoid and correct mistakes.
3.3.1 (A) If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.*
Error Identification
3.3.2 (A) Labels or instructions are provided when content requires user input.*
Labels or Instructions
3.3.3 (AA) If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.*
Error Suggestion
3.3.4 (AA) For web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Submissions are reversible. Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.*
Error Prevention (Legal, Financial, Data)
3.3.7 (A) Information previously entered by the user that is required to be entered again in the same process is either auto-populated, or available for the user to select. Except when: re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid.*
Redundant Entry
3.3.8 (AA) A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Another authentication method that does not rely on a cognitive function test. A mechanism is available to assist the user in completing the cognitive function test. The cognitive function test is to recognize objects. The cognitive function test is to identify non-text content the user provided to the website.*
Accessible Authentication (Minimum)

4. Robust

Website content should be able to be interpreted reliably by a wide variety of user agents.
4.1 Compatible

Ensure compatibility with current and future user agents, including assistive technologies.
4.1.2 (A) For all user interface components the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.*
Name, Role, Value
4.1.3 (AA) In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.Intent*
Status Messages

Compliance Documentation
Documentation From An Accessibility Checker

Regardless of your compliance status, please upload screenshots or similar documentation from Mauve or ObservePoint for the following subset of your webpages:
- The homepage
- The top 10 most-visited pages (in addition to the homepage)
- At least one page of each type/template (e.g. event, blog post, article, etc.)
Upload Documentation From Mauve, ObservePoint, or any accurate Accessibility Checker *

Please make sure your checker indicates accessibility criteria violations (when necessary). Supported file types: pdf, doc, docx, xls, xlsx, txt, rtf, jpg, jpeg, png
Cancelof
Documentation From A Contract

If you have a contract or guarantee from your website vendor/developer guaranteeing that the site meets any level of accessibility standards, please upload it.
Upload Documentation From A Contract

Supported file types: pdf, doc, docx, xls, xlsx, txt, rtf, jpg, jpeg, png
Cancelof
Should be Empty:

Birmingham Digital Resource Accessibility Audit

1. Perceivable

1.1 Text Alternatives

1.2 Time-based Media

1.3 Adaptable

1.4 Distinguishable

2. Operable

2.1 Keyboard Accessible

2.2 Enough Time

2.3 Seizures and Physical Reactions

2.4 Navigable

2.5 Input Modalities

3. Understandable

3.1 Readable

3.2 Predictable

3.3 Input Assistance

4. Robust

4.1 Compatible

Compliance Documentation

Documentation From An Accessibility Checker

Documentation From A Contract