Breaking Digital Barriers

An accessibility audit of AndNowSheRises.org to better support all visitors, including those with disabilities

Role

UX Designer and Accessibility Auditor

Team

Solo project

Timeline

7 hours

Tools

Web Content Accessibility Guidelines (WCAG), Chrome's CC checker, NVDA screen reader, AXE DevTools
Overview

My approach used a mix of manual testing and automated tools

And Now She Rises is a non-profit dedicated to helping abused women reclaim their lives. The founders asked me to identify any accessibility issues visitors to their website might encounter. I reviewed four key pages (Home, Press, Impact, Panel Talks).

homepage of andnowsherises.org
Step 1

Initial observation based on WCAG guidelines

WCAG Principle #1
Perceivable
People need to be able to see, hear, or otherwise sense the information
WCAG Principle #2
Operable
People need to be able to navigate and interact with your website effectively
WCAG Principle #3
Understandable
People need to be able to understand the info and how to use your website
WCAG Principle #4
Robust
Your website needs to work well with different tools, now and in the future
Satisfactory Findings

What's working well

Website is fully responsive to different viewports
Text resizing is supported
No flashing content
Navigation through header
Logical focus order
Error messages are clear and helpful
Unsatisfactory Findings

Improvement opportunities

Auto-rotating carousel without control buttons
Insufficient color contrast
Form fields use placeholder text instead of labels
Missing alt text for images
Lack of audio descriptions and subtitles for podcast clip
Missing visible focus indicators
header highlight "missing visible focus indicators: makes it difficult for keyboard users to see which link they are currently on
Header

A closer look at missing visible focus indicators: Users with disabilities, such as motor impairments, often rely on the keyboard to navigate websites. As they press the Tab key to move through interactive elements like buttons, links, and form fields, they expect a clear visual indicator (such as a border or highlight) to show which element is currently in focus. Without a focus indicator, navigation becomes difficult or impossible.

Step 2

Analysis using Chrome's CC Checker

Key Findings

Areas of low contrast make text difficult to read

I tested the contrast of 3 prominent color combinations and found their contrast ratios were well under the minimum accessible contrast ratio of 4.5:1.

The gray text on the white background has a contrast ratio of 1.47:1
The white text on the coral pink gradient background has a contrast ratio of 2.59:1 at its lightest point and 2.84:1 at its darkest
The coral pink text on the white background has a contrast ratio of 2.84:1
4 low contrast areas highlighted on the homepage
Homepage
Contrast check result Contrast Check result 2Contrast check result 3
Contrast test results of 3 prominent color combinations
Step 3

Analysis using AXE DevTool

Key Findings

Automated scanning surfaced additional technical issues

AXE analyzes the coding of websites. When inspecting the 4 main pages, I found a number of serious and critical issues:

Insufficient color contrast
Missing accessible title for iframe
Invalid ARIA roles and attributes
Missing alt text for images
Screenshot from an AXE DevTool testScreenshot from an AXE DevTool test
Findings from AXE DevTool tests
Step 4

Evaluation using the NVDA screen reader

Key Findings

Testing highlighted issues that hinder screen reader combability

Using a screen reader allowed me to experience firsthand several errors that made navigating the website and understanding the content challenging.

Auto-rotating carousel without control buttons
Missing landmarks for sign-up and subscribe sections
Misnamed Facebook link
Form fields use placeholder text instead of labels
Skipped heading levels
Missing alt text for images
 example of images without alt text "Missing Alt Text: Makes images unable to provide valuable context to visually impaired users"
Image and data illustration without alt text on the Impact page

A closer look at missing alt text for images: Images throughout the And Now She Rises website play a key role in telling the non-profit's story by showing community involvement, event scale, and the impact of its activities. Without alt text to describe the image, visually impaired users miss out on this visual story and the important data that illustrates the non-profit's amazing impact.

Step 5

Issue prioritization and next steps

High-Priority Recommendations

I found 8 issues that severely impact users

Screenshot with accessibility issues highlightedScreenshot with accessibility issues highlighted
Screenshot with accessibility issues highlightedScreenshot with accessibility issues highlighted
High Priority Issue #1

Insufficient color contrast (all pages)

The text doesn’t stand out enough from the background because the colors are too similar. Low contrast can make reading difficult for everyone, but it’s especially challenging for people with visual impairments.

To address this, replace the text color #D0D0D0 with #515151 in order to raise the contrast to 7.6:1. To make the text on the homepage more readable, I would replace the current background and text colors #FD7076 and #FE5E78 with #C40D65 to raise the contrast to 5.79:1.

WCAG 2.2 Criterion: 1.4.3 Contrast (Minimum) - Text should have a contrast ratio of at least 4.5:1 to ensure readability.
Before
After
Before
After
Before
After
High Priority Issue #2

Missing alt text for images (all pages)

Alt text is crucial for users who can’t see images, as it allows them to understand the content through a screen reader.

To address this, add descriptive alt attributes to all meaningful images, and use empty alt for decorative images

WCAG 2.2 Criterion: 1.1.1 Non-text Content - All non-text content, like images, must have a text alternative that serves the same purpose.
High Priority Issue #3

Auto-rotating image carousel (Impact)

The carousel (slideshow) moves automatically and doesn’t have buttons to pause or control it. Auto-rotating content can be frustrating and hard to follow, especially for users with cognitive or motor disabilities.

To address this, add control buttons and a pause function to the carousel to give users more control over the content.

WCAG 2.2 Criterion: 2.2.2 Pause, Stop, Hide - Users must be able to pause, stop, or hide moving content.
High Priority Issue #4

Placeholder text used as labels (Homepage, Impact)

Forms use placeholder text inside the input fields instead of clear labels outside. Labels outside the input fields are crucial because placeholder text disappears when users type, which can be confusing, especially for people with cognitive disabilities or who use screen readers.

To address this, ensure each form field has a clear, visible label outside the input field to improve clarity and usability.

WCAG 2.2 Criterion: 3.3.2 Labels or Instructions - Provide labels or instructions for all form fields to ensure users understand what information is required.
Before
After
High Priority Issue #5

Missing subtitles or transcript in audio content (Panel Talks)

The embedded podcast clip doesn’t offer subtitles or a transcript. Without these options, users who can’t hear the audio won’t know what’s being said, excluding them from the content.

To address this, provide a link to a transcript directly below the player or use an alternative media player that supports captions

WCAG 2.2 Criterion: 1.2.1 Audio-only and Video-only (Prerecorded) - Provide a text alternative for all audio content to ensure everyone can access the information.
High Priority Issue #6

Missing visible focus indicators (all pages)

When navigating with a keyboard, it’s hard to see which part of the page is currently selected or “in focus”. People who use keyboards instead of a mouse rely on focus indicators to know where they are on a page.

To address this, implement visible focus indicators using CSS to ensure that all interactive elements are easily identifiable when navigated by keyboard.

WCAG 2.2 Criterion: 2.4.7 Focus Visible - Ensure that when a user navigates using a keyboard, the focused element is clearly visible.
High Priority Issue #7

Invalid ARIA roles and attributes (Panel Talks)

The SoundCloud player uses incorrect ARIA roles and attributes (e.g., aria-role="img" and role="bar"), which can confuse assistive technologies and hinder accessibility.

To address this, replace aria-role="img" with the correct role="img" attribute. Replace role="bar" with role="progressbar", and include relevant ARIA attributes like aria-valuenow, aria-valuemin, and aria-valuemax to fully describe the progress bar's state.

WCAG 2.2 Criterion: 4.1.2 Name, Role, Value - Ensure that all interface components have proper roles and states so that they work correctly with assistive technologies.
High Priority Issue #8

Missing accessible title for iframe (Panel Talks)

The iframe containing the SoundCloud player does not have a title, making it difficult for screen reader users to understand what content is embedded.

To address this, add a descriptive title to the iframe, such as "Podcast clip: Interview with John Doe," to provide context for screen readers.

WCAG 2.2 Criterion: 4.1.2 Name, Role, Value - Ensure that all interface components have proper roles and states so that they work correctly with assistive technologies.

Let's Connect!

Send me an email