Cloudflare Dashboard Now Meets WCAG 2.1 AA and Section 508 Standards
Cloudflare has announced that its primary dashboard now conforms to industry accessibility standards, including WCAG 2.1 AA and Section 508 of the US Rehabilitation Act. The company has also completed a Voluntary Product Accessibility Template (VPAT) to document its current level of conformance.
The work stems from a 2021 audit conducted with third-party experts, which produced a 213-page report cataloging compliance gaps across the dashboard. The audit revealed that keyboard users and screen reader users—who often rely on assistive technologies due to low vision, motor disabilities, or cognitive conditions—were not adequately supported.
Over the following year, the team resolved roughly 400 Jira tickets and built more than 25 new accessible web components. The remediation effort touched forms, data visualizations, heading structure, SVGs, color usage, and numerous long-standing HTML bugs.
Rebuilding Core Components
The internal form component library was rewritten with accessibility as a priority. Changes include improved validation and error handling, explicit labels, required-field annotations, and persistent input descriptions instead of placeholders. These upgraded components were then rolled out across the entire dashboard.
Page structure was corrected by replacing hardcoded heading levels with a technique from Heydon Pickering that uses React Context and arithmetic to manage heading levels dynamically. SVGs are now labeled appropriately and only exposed to assistive technology when they convey useful information.
The team also upgraded several major versions of outdated node modules that the UI components depend on, overhauled color usage with a new set of accessible sequential colors in the design system, and fixed a large number of bugs—most commonly incorrect or unsemantic HTML elements, such as using a generic element where a table row or table cell was required.
Case Study: Making Analytics Charts Accessible
Data visualizations presented one of the most complex challenges. Many charts failed WCAG success criterion 1.4.1 because they relied on color alone to differentiate data series—for instance, using blue for 200 OK responses and orange for 403 Forbidden with no other distinguishing feature.
The UI team focused first on the time series graph component. They experimented with patterns recommended by accessibility experts, including terminal glyphs, dashed line styles, and varied line weights. These approaches proved unusable with real-world data. Terminal glyphs piled up and became indistinguishable, and line pattern differences were too subtle to parse.
The final design eliminated both glyphs and patterns, relying on a simplified interface that fades unfocused data items and uses the new sequential colors. The fading technique carried over from the intermediate iteration and was approved by accessibility and data visualization experts alongside the design and engineering teams.
Engineering work followed the design decisions. To meet WCAG success criterion 2.1.1, the time series graphs were rewritten for full keyboard access: every data point has focus handling, and users can traverse data with arrow keys.
For screen reader support, the team removed auditory "chartjunk" and cleaned up decontextualized data—numbers that screen readers announced without the necessary context from x- and y-axis labels. To satisfy WCAG 1.1.1, new UI component wrappers were built to make chart data downloadable in CSV format. This CSV export capability was deployed across all charts and graphs in the dashboard, not just the time series charts.
Ongoing Work
Applying this level of accessibility treatment to every data visualization in the dashboard remains a work in progress. The team continues to update chart and graph components and notes that the project required a separate, specialized data visualization audit, close collaboration between engineering and design, and that breaking changes were part of the process. The dashboard improvements referenced in this post apply specifically to Cloudflare's primary authenticated web platform, not product-specific dashboards, marketing materials, or third-party integrations.
