Skip to content
https://readwrite.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Alt Text Quality
Action
22 of 124 images have issues
FIX
22 of 124 images have issues
Critical::
21 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with filename as alt text
Info::
25 image(s) with alt text over 125 characters
Info::
47 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
124 images 30 good alt text 47 decorative 1 generic 21 missing
IssueCount
missing21 image(s)
filename1 image(s)
too long25 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
5 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
1 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ReadWrite ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

2 pass 18 fail WCAG AA
h1 Latest News
1.14:1
#000000
on
#161316
needs 3.0:1 (large text)
32px · bottom of viewport
h2 A Secure and Trusted Guide for Smarter P…
1.14:1
#000000
on
#161316
needs 3.0:1 (large text)
24px · bottom of viewport
h3 1.4M
1.14:1
#000000
on
#161316
needs 3.0:1 (large text)
19px · bottom of viewport
h3 35K
1.14:1
#000000
on
#161316
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Trusted
1.14:1
#000000
on
#161316
needs 3.0:1 (large text)
19px · bottom of viewport
h3 5000+
1.14:1
#000000
on
#161316
needs 3.0:1 (large text)
19px · bottom of viewport
h3 20+
1.14:1
#000000
on
#161316
needs 3.0:1 (large text)
19px · bottom of viewport
a Online Casinos
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · top of page (header area)
a Casino Games
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · top of page (header area)
a Crypto Games
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
a International Casinos
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
span Best Of
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
a Offshore Casinos
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
a Casino Bonuses
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
a Fastest Payout Online Casinos
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
a Mobile Casinos
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
span Casino Guides
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
a Online Gambling Guide
1.14:1
#000000
on
#161316
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Latest News1.14:13.0:1
#000000
#161316
Fail
h2 A Secure and Trusted…1.14:13.0:1
#000000
#161316
Fail
h3 1.4M1.14:13.0:1
#000000
#161316
Fail
h3 35K1.14:13.0:1
#000000
#161316
Fail
h3 Trusted1.14:13.0:1
#000000
#161316
Fail
h3 5000+1.14:13.0:1
#000000
#161316
Fail
h3 20+1.14:13.0:1
#000000
#161316
Fail
title ReadWrite - iGaming …21.00:14.5:1
#000000
#FFFFFF
Pass
a Casino8.16:14.5:1
#000000
#A2A1A2
Pass
a Online Casinos1.14:14.5:1
#000000
#161316
Fail
a Casino Games1.14:14.5:1
#000000
#161316
Fail
a Crypto Games1.14:14.5:1
#000000
#161316
Fail
a International Casino…1.14:14.5:1
#000000
#161316
Fail
span Best Of1.14:14.5:1
#000000
#161316
Fail
a Offshore Casinos1.14:14.5:1
#000000
#161316
Fail
a Casino Bonuses1.14:14.5:1
#000000
#161316
Fail
a Fastest Payout Onlin…1.14:14.5:1
#000000
#161316
Fail
a Mobile Casinos1.14:14.5:1
#000000
#161316
Fail
span Casino Guides1.14:14.5:1
#000000
#161316
Fail
a Online Gambling Guid…1.14:14.5:1
#000000
#161316
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 82/100 — 4 failing, 20 passed
REVIEW
82

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.rw-banner-inner > div.rw-banner-bg-img > picture.skiplazy > img div.rw-banner-inner > div.rw-banner-bg-img > picture.skiplazy > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header > div.header_container > div.header_search > a.btn div.header > div.header_container > div.header_search > a.btn
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-as-seen-inner > ul > li > a div.rw-as-seen-inner > ul > li > a
div.rw-social-media-ft > ul > li > a div.rw-social-media-ft > ul > li > a
div.rw-social-media-ft > ul > li > a div.rw-social-media-ft > ul > li > a
div.rw-social-media-ft > ul > li > a div.rw-social-media-ft > ul > li > a
div.rw-social-media-ft > ul > li > a div.rw-social-media-ft > ul > li > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GAMBLING Fresno Arts Council ex manager admits $1.8M theft spent on gambling SU… div.col-lg-12 > div.rw-latest-news-iiner2 > div.col-lg-6 > ul
div.col-lg-12 > div.rw-as-seen-outer > div.rw-as-seen-inner > ul div.col-lg-12 > div.rw-as-seen-outer > div.rw-as-seen-inner > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BETTING div.row > div.rw-banner-inner > div.rw-banner-box-inner > a.rw-cat-namecl
GAMBLING ul > li > div.rw-home-right-innercl > a.rw-cat-namecl
PREDICTION MARKETS ul > li > div.rw-home-right-innercl > a.rw-cat-namecl
PREDICTION MARKETS ul > li > div.rw-home-right-innercl > a.rw-cat-namecl
GAMBLING div.row > div.rw-banner-inner > div.rw-banner-box-inner > a.rw-cat-namecl
GAMBLING div.rw-guide-box-outer > div.rw-box-inner > div.rw-trending-text > a.rw-cat-namecl
CASINO div.rw-guide-box-outer > div.rw-box-inner > div.rw-trending-text > a.rw-cat-namecl
BETTING div.rw-guide-box-outer > div.rw-box-inner > div.rw-trending-text > a.rw-cat-namecl
BETTING div.rw-guide-box-outer > div.rw-box-inner > div.rw-trending-text > a.rw-cat-namecl

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Hierarchy
44 headings
PASS
44 headings
Info::
Single H1 present
  • H1 Latest News
  • H2 German regulator targets Capital Bra over alleged illegal gambling promotion case
  • H3 Fresno Arts Council ex manager admits $1.8M theft spent on gambling
  • H3 Fanatics Markets launches Combos feature as basketball postseason trading starts
  • H3 Arizona court battle against Kalshi slows amid legal scope disputes
  • H3 Evoke takeover talks by Bally’s Intralot confirm pressure on gambling group finances
  • H3 Gambling ads face scrutiny as Google blocks 270 million promotions in 2025
  • H3 Lumbee Council advances gaming amendment in North Carolina, sending measure to tribal voters soon
  • H3 DraftKings Alberta entry signals Canada gambling market legal shift ahead
  • H3 Michigan approves bet365 launch as Odawa partner, replacing PokerStars
  • H3 UK High Court ends National Lottery license fight with Allwyn victory
  • H3 New York lawsuit says Stake and Coinbase targeted child gambler for years
  • H3 Maryland session ends leaving sweepstakes gaming bills stalled once again as SGLA celebrates
  • H3 CFTC’s one-man show gets awkward on the Hill as lawmakers hammer Selig on sports bets, staffing gaps and corruption claims
  • H3 Yocha Dehe slams Vallejo Council over rushed casino deal approval process
  • H3 NCAA seeks faster trial over DraftKings disputed March Madness branding case
  • H3 Iowa lawmakers advance bill tightening rules on prediction markets
  • H3 Louisiana lawmakers advance crackdown targeting illegal online sweepstakes
  • H3 South Carolina lawsuit says Dave & Buster’s games are illegal gambling
  • H3 Kalshi challenges Ohio over proposed $5M regulatory fine
  • H3 Arizona ruling enters Wisconsin Ho-Chunk Nation fight against Kalshi
  • H3 Minnesota advances controversial felony ban on prediction markets as scrutiny grows
  • H3 Ohio moves to fine Kalshi $5M over illegal sports betting
  • H3 Oakland police raid suspected illegal gambling site, detaining ten people
  • H2 Casino<img width="16" height="17" src="https://readwrite.com/wp-content/themes/twentytwentyone-child/images/Arrow-right.svg"alt="Arrow right">
  • H3 Lumbee Council advances gaming amendment in North Carolina, sending measure to tribal voters soon
  • H3 Yocha Dehe slams Vallejo Council over rushed casino deal approval process
  • H3 Spanberger veto blocks Fairfax casino vote amid clash over local control
  • H2 Betting<img width="16" height="17" src="https://readwrite.com/wp-content/themes/twentytwentyone-child/images/Arrow-right.svg"alt="Arrow right">
  • H3 DraftKings Alberta entry signals Canada gambling market legal shift ahead
  • H3 Michigan approves bet365 launch as Odawa partner, replacing PokerStars
  • H3 Online sports betting grows rapidly as concerns about risks rise across the US, survey shows
  • H2 Poker<img width="16" height="17" src="https://readwrite.com/wp-content/themes/twentytwentyone-child/images/Arrow-right.svg"alt="Arrow right">
  • H3 FanDuel approved for multi-state poker network expansion in Michigan
  • H3 Killing of Westfield poker player Matt Lushin reveals tensions beyond the table
  • H3 Thomas Goldstein convicted in sweeping federal tax case: high-stakes poker and the fall of a Supreme Court lawyer
  • H2 A Secure and Trusted Guide for Smarter Play
  • H3 1M
  • H3 1.4M
  • H3 35K
  • H3 Trusted
  • H3 5000+
  • H3 20+
  • H4 Popular Topics<img width="16" height="17" src="https://readwrite.com/wp-content/themes/twentytwentyone-child/images/Arrow-right.svg" alt="Arrow right.svg"/>
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="search-input">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputtext(Search news, guides and reviews)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s" id="search-input">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback