Xx.com
Accessibility Score
Issues Found
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: 8.4pt (11.25px), 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: bold). 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
Serious<svg> elements with an img role must have alternative text2 elements
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.
Failing 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">
Fix any of the following:
- Element has no child that is a title
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<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">
Fix any of the following:
- Element has no child that is a title
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
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">
Fix any of the following:
- user-scalable on <meta> tag disables zooming on mobile devices
Passed Audits
<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 dir="ltr" lang="en" style="overflow-y: scroll; overscroll-behavior-y: none; font-size: 15px; color-scheme: 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 dir="ltr" lang="en" style="overflow-y: scroll; overscroll-behavior-y: none; font-size: 15px; color-scheme: light;">
All page content should be contained by landmarks189 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 id="react-root" style="height:100%;display:flex;">
<div class="css-175oi2r r-13awgt0 r-12vffkv">
<div class="css-175oi2r r-13awgt0 r-12vffkv">
<div class="r-zchlnj r-1d2f490 r-u8s1d r-ipm5af" id="layers" style="z-index: 1;">
<div class="css-175oi2r r-aqfbo4 r-zchlnj r-1d2f490 r-1xcajam r-1p0dtai r-12vffkv">
<div class="css-175oi2r r-12vffkv" style="position: absolute; bottom: 0px; width: 100%; transition: transform 200ms ease-out; transform: translateY(0px);"><div class="css-175oi2r r-12vffkv"><div class="css-175oi2r" data-testid="BottomBar"></div></div></div>
<div class="css-175oi2r r-12vffkv"><div class="css-175oi2r" data-testid="BottomBar"></div></div>
<div class="css-175oi2r" data-testid="BottomBar"></div>
<div class="css-175oi2r r-1f2l425 r-13qz1uu r-417010">
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
Showing first 10 of 189 audited elements.
ARIA attributes must be used as specified for the element's role1 element
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
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
ARIA attributes must conform to valid names1 element
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
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
ARIA attributes must conform to valid values1 element
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
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
ARIA hidden element must not be focusable or contain focusable elements1 element
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
<input type="password" name="password" tabindex="-1" aria-hidden="true" class="jf-element" value="" style="position: absolute; top: 0px; left: 0px; width: 100%; height: 100%; opacity: 0; pointer-events: none;">
ARIA role should be appropriate for the element23 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
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
<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">
<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">
<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">
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
<a href="https://about.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com/using-x/download-the-x-app" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://grok.com/" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/tos" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
Showing first 10 of 23 audited elements.
ARIA roles used must conform to valid values22 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
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
<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">
<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">
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
<a href="https://about.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com/using-x/download-the-x-app" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://grok.com/" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/tos" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/privacy" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
Showing first 10 of 22 audited elements.
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 style="background-color: rgb(255, 255, 255); scrollbar-color: rgb(185, 202, 211) rgb(247, 249, 249);" data-theme="light">
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 type="text" autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" name="username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" value="">
Buttons must have discernible text2 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">
Deprecated ARIA roles must not be used22 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
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
<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">
<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">
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
<a href="https://about.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com/using-x/download-the-x-app" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://grok.com/" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/tos" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/privacy" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
Showing first 10 of 22 audited elements.
Document 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.
Audit Elements
<html dir="ltr" lang="en" style="overflow-y: scroll; overscroll-behavior-y: none; font-size: 15px; color-scheme: light;">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
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 dir="ltr" lang="en" style="overflow-y: scroll; overscroll-behavior-y: none; font-size: 15px; color-scheme: light;">
Elements must meet minimum color contrast ratio thresholds28 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 style="font-family: Geist, "Helvetica Neue", Helvetica, Arial, sans-serif; font-weight: 600; font-size: 64px; letter-spacing: -1px; line-height: 0.9; margin-bottom: 32px; padding-bottom: 16px; color: rgb(26, 26, 26);">Happening now.</h1>
<p class="jf-element">Continue with phone</p>
<p class="jf-element">Continue with Apple</p>
<p class="jf-element">or</p>
<input type="text" autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" name="username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" value="">
<input type="password" name="password" tabindex="-1" aria-hidden="true" class="jf-element" value="" style="position: absolute; top: 0px; left: 0px; width: 100%; height: 100%; opacity: 0; pointer-events: none;">
<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>
<span class="css-1jxf684 r-bcqeeo r-1ttztb7 r-qvutc0 r-poiln3">About</span>
Showing first 10 of 28 audited elements.
Elements must only use permitted ARIA attributes1 element
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
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
Elements must only use supported ARIA attributes1 element
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
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
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 type="text" autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" name="username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" value="">
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 type="text" autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" name="username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" value="">
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 type="text" autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" name="username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" value="">
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_115432_828333" 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_115432_828333" 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 style="font-family: Geist, "Helvetica Neue", Helvetica, Arial, sans-serif; font-weight: 600; font-size: 64px; letter-spacing: -1px; line-height: 0.9; margin-bottom: 32px; padding-bottom: 16px; color: rgb(26, 26, 26);">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 style="font-family: Geist, "Helvetica Neue", Helvetica, Arial, sans-serif; font-weight: 600; font-size: 64px; letter-spacing: -1px; line-height: 0.9; margin-bottom: 32px; padding-bottom: 16px; color: rgb(26, 26, 26);">Happening now.</h1>
IDs used in ARIA and labels must be unique1 element
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
<input type="text" autocomplete="username webauthn" inputmode="text" id="jf-input-username_or_email" name="username_or_email" pattern="^[a-zA-Z0-9@._+\-]+$" class="jf-element jf-float-input" value="">
Inline text spacing must be adjustable with custom stylesheets30 elements
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
<html dir="ltr" lang="en" style="overflow-y: scroll; overscroll-behavior-y: none; font-size: 15px; color-scheme: light;">
<body style="background-color: rgb(255, 255, 255); scrollbar-color: rgb(185, 202, 211) rgb(247, 249, 249);" data-theme="light">
<div id="react-root" style="height:100%;display:flex;">
<div class="r-zchlnj r-1d2f490 r-u8s1d r-ipm5af" id="layers" style="z-index: 1;">
<h1 style="font-family: Geist, "Helvetica Neue", Helvetica, Arial, sans-serif; font-weight: 600; font-size: 64px; letter-spacing: -1px; line-height: 0.9; margin-bottom: 32px; padding-bottom: 16px; color: rgb(26, 26, 26);">Happening now.</h1>
<div class="S9gUrf-YoZ4jf" style="position: relative;">
<iframe src="https://accounts.goo..." class="L5Fo6c-PQbLGe" allow="identity-credentials..." id="gsi_115432_828333" title="Sign in with Google ..." style="display: block; posi...">
<div class="jf-element" style="position: fixed; bottom: 1rem; margin-top: 1rem; left: 50%; transform: translateX(-50%); z-index: 1000; display: flex; flex-direction: column; align-items: center; flex-shrink: 1; animation: 0.3s ease-out 0s 1 normal none running slideUp;">
<div style="flex: 1 1 0%; display: flex; justify-content: flex-end; align-items: center; overflow: hidden; min-height: 45vh;">
<svg fill="none" viewBox="0 0 480 490" xmlns="http://www.w3.org/2000/svg" style="width: 100%; max-width: 480px; height: auto;">
Showing first 10 of 30 audited elements.
Interactive controls must not be nested4 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">
<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">
<button type="button" class="jf-element">
<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">
Interactive elements must have a visible focus indicator21 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 href="https://about.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r..." style="color: rgb(83, 100, 113);">
<a href="https://help.x.com/using-x/download-the-x-app" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r..." style="color: rgb(83, 100, 113);">
<a href="https://grok.com/" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r..." style="color: rgb(83, 100, 113);">
<a href="https://help.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r..." style="color: rgb(83, 100, 113);">
<a href="https://x.com/tos" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r..." style="color: rgb(83, 100, 113);">
<a href="https://x.com/privacy" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r..." style="color: rgb(83, 100, 113);">
<a href="https://support.x.com/articles/20170514" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r..." style="color: rgb(83, 100, 113);">
Showing first 10 of 21 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
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
Links must have discernible text21 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 href="https://about.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com/using-x/download-the-x-app" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://grok.com/" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/tos" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/privacy" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://support.x.com/articles/20170514" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
Showing first 10 of 21 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
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 dir="ltr" lang="en" style="overflow-y: scroll; overscroll-behavior-y: none; font-size: 15px; color-scheme: 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 dir="ltr" lang="en" style="overflow-y: scroll; overscroll-behavior-y: none; font-size: 15px; color-scheme: light;">
Required ARIA attributes must be provided22 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
<main role="main" class="css-175oi2r r-16y2uox r-1wbh5a2">
<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">
<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">
<nav aria-label="Footer" role="navigation" class="css-175oi2r r-18u37iz r-1w6e6rj r-3pj75a r-1777fci r-1mmae3n">
<a href="https://about.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com/using-x/download-the-x-app" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://grok.com/" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://help.x.com" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/tos" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
<a href="https://x.com/privacy" dir="ltr" rel="noopener noreferrer nofollow" target="_blank" role="link" class="css-146c3p1 r-bcqeeo r-1ttztb7 r-qvutc0 r-37j5jr r-1gkfh8e r-56xrmm r-16dba41 r-1loqt21" style="color: rgb(83, 100, 113);">
Showing first 10 of 22 audited elements.
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">