X x.com
Accessibility score
League position
5thof 10
Issues found
5
Audits passed
45
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousElements must meet minimum color contrast ratio thresholds4 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Failing Elements
<span class="jf-element jf-float-label">Email or username</span>
Fix any of the following:
- Element has insufficient color contrast of 2.77 (foreground color: #0ea5e9, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<p class="jf-element">Continue</p>
Fix any of the following:
- Element has insufficient color contrast of 3.23 (foreground color: #78716c, background color: #d4d4d4, font size: 12.8pt (17px), font weight: normal). Expected contrast ratio of 4.5:1
<span class="jf-element j-vmpu780 j-azowe50 j-2vsp8w0">By continuing, you agree to our </span>
Fix any of the following:
- Element has insufficient color contrast of 3.94 (foreground color: #808080, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<span class="jf-element j-vmpu780 j-azowe50 j-2vsp8w0"> and </span>
Fix any of the following:
- Element has insufficient color contrast of 3.94 (foreground color: #808080, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
ModerateDocument should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Failing Elements
<html lang="en" dir="ltr" data-app-env="prod" data-app-version="07070c385ca02744ff9d469bf3a235937af119bd" data-theme="light">
Fix all of the following:
- Document does not have a main landmark
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Failing Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModerateZooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Failing Elements
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=0,viewport-fit=cover" nonce="">
Fix any of the following:
- user-scalable on <meta> tag disables zooming on mobile devices
ModerateAll page content should be contained by landmarks6 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<h1 class="mb-8 pb-4 text-center text-[50px] leading-[0.9] font-semibold text-[#1A1A1A] min-[851px]:text-start min-[851px]:text-[64px] min-[851px]:tracking-[-1px] dark:text-white">Happening now<!-- -->.</h1>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="jf-element flex j-ou8jrn0 j-by1qh80 j8vunac0 j-4jzft30">
Fix any of the following:
- Some page content is not contained by landmarks
<span class="jf-element jf-float-label">Email or username</span>
Fix any of the following:
- Some page content is not contained by landmarks
<input autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" type="text" value="" name="username_or_email">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="jf-element flex jfa278c0 jqjp5430 j8vunac0 j-by1qh80 j-pmlt8x0 j-dlswat0 jllpup913 jllpup911 jvbtivl12"><div class="jf-element flex j-ou8jrn0 j8vunac0 j-by1qh80"><div class="jf-element text-text j-a8kd9c0 j-nasjnf0 j-vmpu780 j-tboqzj0"><p class="jf-element">Continue</p></div></div></div>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="jf-element flex jy49p8z0 jyks6vd0">
Fix any of the following:
- Some page content is not contained by landmarks
Passed audits45 across 1 page
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en" dir="ltr" data-app-env="prod" data-app-version="07070c385ca02744ff9d469bf3a235937af119bd" data-theme="light">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en" dir="ltr" data-app-env="prod" data-app-version="07070c385ca02744ff9d469bf3a235937af119bd" data-theme="light">
<svg> elements with an img or image role must have alternative text1 element
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
All page content should be contained by landmarks120 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div class="flex min-h-dvh flex-1 flex-col">
<div class="mx-auto flex w-full max-w-7xl flex-1 max-[500px]:hidden">
<div class="flex flex-1 items-center justify-center px-4 py-10 min-[851px]:justify-start min-[851px]:ps-9">
<div class="w-full max-w-[400px]">
<div class="min-h-[440px] w-full overflow-hidden">
Showing first 5 of 120 audited elements.
Alternative text of images should not be repeated as text1 element
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img alt="" width="160" height="160" loading="lazy" fetchpriority="low" class="two-col:size-[112px] nav-xxl:size-[144px] size-[96px] dark:invert" src="https://abs.twimg.com/x-web/x-web/assets/scan-to-get-app-qr-BrLDtiAI.svg">
ARIA attributes must be used as specified for the element's role5 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
<div aria-live="polite" aria-atomic="true" class="sr-only"></div>
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
ARIA attributes must conform to valid names5 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
<div aria-live="polite" aria-atomic="true" class="sr-only"></div>
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
ARIA attributes must conform to valid values5 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
<div aria-live="polite" aria-atomic="true" class="sr-only"></div>
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
ARIA commands must have an accessible name1 element
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
ARIA hidden element must not be focusable or contain focusable elements8 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" data-icon="icon-phone-stroke" viewBox="0 0 24 24" width="22" height="22" display="flex" role="img" aria-hidden="true">
<div aria-hidden="true" class="jf-element jf-gsi-face pointer-events-none relative flex h-10 items-center justify-center overflow-hidden rounded-full border j-jvnxsw0 jfa278c0 j-e0iegv0 j-xqrfhb0 jdyswd217">
<svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" data-icon="icon-logo-apple" viewBox="0 0 24 24" width="22" height="22" display="flex" role="img" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" data-icon="icon-logo-apple" viewBox="0 0 24 24" width="22" height="22" display="flex" role="img" aria-hidden="true">
<svg viewBox="0 0 24 24" id="loading-x-anim-0" aria-hidden="true" class="r-1p0dtai r-13gxpu9 r-4qtqp9 r-yyyyoo r-wy61xf r-1d2f490 r-6qdh9c r-ywje51 r-dnmrzs r-u8s1d r-zchlnj r-1plcrui r-ipm5af r-lrvibr r-1blnp2b">
Showing first 5 of 8 audited elements.
ARIA role should be appropriate for the element10 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[140px]">
<svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" data-icon="icon-phone-stroke" viewBox="0 0 24 24" width="22" height="22" display="flex" role="img" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" data-icon="icon-logo-google" viewBox="0 0 24 24" width="1em" height="1em" display="flex" role="img" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" data-icon="icon-logo-google-g-color" viewBox="0 0 24 24" width="22" height="22" display="flex" role="img" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" data-icon="icon-logo-google-g-color" viewBox="0 0 24 24" width="22" height="22" display="flex" role="img" aria-hidden="true">
Showing first 5 of 10 audited elements.
ARIA roles used must conform to valid values2 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body>
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<input autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" type="text" value="" name="username_or_email">
Buttons must have discernible text3 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button type="button" class="jf-element jmm2vci0 j-5ger9i0 j-d7h1p60 jzedevn100">
<button type="button" class="jf-element">
<button type="button" class="border-normal shadow...">
Content must reflow without two-dimensional scrolling0 elements
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer>
Deprecated ARIA roles must not be used2 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer>
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en" dir="ltr" data-app-env="prod" data-app-version="07070c385ca02744ff9d469bf3a235937af119bd" data-theme="light">
Elements marked as presentational should be consistently ignored1 element
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img alt="" width="160" height="160" loading="lazy" fetchpriority="low" class="two-col:size-[112px] nav-xxl:size-[144px] size-[96px] dark:invert" src="https://abs.twimg.com/x-web/x-web/assets/scan-to-get-app-qr-BrLDtiAI.svg">
Elements must meet minimum color contrast ratio thresholds24 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<h1 class="mb-8 pb-4 text-center text-[50px] leading-[0.9] font-semibold text-[#1A1A1A] min-[851px]:text-start min-[851px]:text-[64px] min-[851px]:tracking-[-1px] dark:text-white">Happening now<!-- -->.</h1>
<p class="jf-element">Continue with phone</p>
<span class="jf-element flex items-center justify-center gap-2 font-medium">
<p class="jf-element">Continue with Apple</p>
<p class="jf-element">or</p>
Showing first 5 of 24 audited elements.
Elements must only use permitted ARIA attributes5 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
<div aria-live="polite" aria-atomic="true" class="sr-only"></div>
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
Elements must only use supported ARIA attributes5 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
<div aria-live="polite" aria-atomic="true" class="sr-only"></div>
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
Elements should not have tabindex greater than zero3 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false" data-react-aria-top-layer="true"></section>
Focused elements must not be entirely hidden by author-created content17 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a href="https://x.com/tos" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug...">
<a href="https://x.com/privacy" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug...">
<a href="https://help.x.com/rules-and-policies/twitter-cook..." target="_blank" rel="noopener noreferrer" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug...">
<a target="_blank" rel="noopener noreferrer nofollow" href="https://about.x.com" class="hover:underline">
<a target="_blank" rel="noopener noreferrer nofollow" href="https://help.x.com/using-x/download-the-x-app" class="hover:underline">
Showing first 5 of 17 audited elements.
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" type="text" value="" name="username_or_email">
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" type="text" value="" name="username_or_email">
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" type="text" value="" name="username_or_email">
Frames must have a unique title attribute1 element
Screen reader users navigate frames using a list of frame titles. Duplicate or missing titles make it impossible to distinguish between frames, forcing users to explore each frame's content manually. Unique, descriptive titles enable quick navigation to the correct frame.
Audit Elements
<iframe src="https://accounts.goo..." class="L5Fo6c-PQbLGe" allow="identity-credentials..." id="gsi_419640_543005" title="Sign in with Google ..." style="display: block; posi...">
Frames must have an accessible name1 element
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Audit Elements
<iframe src="https://accounts.goo..." class="L5Fo6c-PQbLGe" allow="identity-credentials..." id="gsi_419640_543005" title="Sign in with Google ..." style="display: block; posi...">
Heading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="mb-8 pb-4 text-center text-[50px] leading-[0.9] font-semibold text-[#1A1A1A] min-[851px]:text-start min-[851px]:text-[64px] min-[851px]:tracking-[-1px] dark:text-white">Happening now<!-- -->.</h1>
Headings should not be empty1 element
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="mb-8 pb-4 text-center text-[50px] leading-[0.9] font-semibold text-[#1A1A1A] min-[851px]:text-start min-[851px]:text-[64px] min-[851px]:tracking-[-1px] dark:text-white">Happening now<!-- -->.</h1>
IDs used in ARIA and labels must be unique2 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<span class="L6cTce" id="button-label">Continue with Google. Opens in new tab</span>
<input autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" type="text" value="" name="username_or_email">
Images must have alternative text1 element
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img alt="" width="160" height="160" loading="lazy" fetchpriority="low" class="two-col:size-[112px] nav-xxl:size-[144px] size-[96px] dark:invert" src="https://abs.twimg.com/x-web/x-web/assets/scan-to-get-app-qr-BrLDtiAI.svg">
Inline text spacing must be adjustable with custom stylesheets1 element
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<div style="align-items:center;animation:slideUp 0.3s ease-out;bottom:1rem;display:flex;flex-direction:column;flex-shrink:1;left:50%;margin-top:1rem;position:fixed;transform:translateX(-50%);z-index:1000" class="jf-element">
Interactive controls must not be nested5 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<button type="button" class="jf-element jmm2vci0 j-5ger9i0 j-d7h1p60 jzedevn100">
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<button type="button" class="jf-element">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
<button type="button" class="border-normal shadow...">
Interactive elements must have a visible focus indicator17 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a href="https://x.com/tos" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug...">
<a href="https://x.com/privacy" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug...">
<a href="https://help.x.com/rules-and-policies/twitter-cook..." target="_blank" rel="noopener noreferrer" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug...">
<a target="_blank" rel="noopener noreferrer nofollow" href="https://about.x.com" class="hover:underline">
<a target="_blank" rel="noopener noreferrer nofollow" href="https://help.x.com/using-x/download-the-x-app" class="hover:underline">
Showing first 5 of 17 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination2 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<footer>
<nav class="text-subtext3 flex flex-wrap items-center justify-center gap-y-1 px-4 py-3 leading-6 text-gray-700">
Links must have discernible text16 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a href="https://x.com/tos" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug11">Terms of Service</a>
<a href="https://x.com/privacy" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug11">Privacy Policy</a>
<a href="https://help.x.com/rules-and-policies/twitter-cookies" target="_blank" rel="noopener noreferrer" class="jf-element j-azowe50 j-a8kd9c0 j-53n1bs12 j-4t3tug11">Cookie Use</a>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://about.x.com" class="hover:underline">About</a>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://help.x.com/using-x/download-the-x-app" class="hover:underline">Get App</a>
Showing first 5 of 16 audited elements.
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en" dir="ltr" data-app-env="prod" data-app-version="07070c385ca02744ff9d469bf3a235937af119bd" data-theme="light">
Page should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Audit Elements
<html lang="en" dir="ltr" data-app-env="prod" data-app-version="07070c385ca02744ff9d469bf3a235937af119bd" data-theme="light">
Required ARIA attributes must be provided2 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<div tabindex="0" role="button" aria-labelledby="button-label" class="nsm7Bb-HzV7m-LgbsSe TzA9Ye-LgbsSe hJDwNd-SxQuSe i5vt6e-Ia7Qfc JGcpL-RbRzK">
<svg aria-label="X" role="img" fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" class="h-auto w-full max-w-[480px]">
Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=0,viewport-fit=cover" nonce="">
How does your site stack up against X?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Social Media
