Skip to main content

Public accessibility report

Your accessibility snapshot

sarhne.sarahah.proصارحني برسالة سرية xxxx

Scanned · https://sarhne.sarahah.pro/431023521112004asmaa#google_vignette

Automated score

28/100

Significant findings

At a glance

Automated findings
9
Highest severity
critical
Letter grade (rough)
F

Axe rules in a real browser. Not a substitute for manual testing.

Score 28/100 based on automated checks — 9 findings, highest severity: critical.

What this means: Treat this as a prioritized to-do list from automation—not proof everything is fixed, and not a substitute for manual checks when it matters.

Address critical and serious items first on real user paths (forms, checkout, navigation). They often block or frustrate people using keyboards or assistive tech.

Findings by severity

2
critical
4
serious
3
moderate
0
minor

This report is not indexed by search engines by default.

Why this order

We list the highest-severity rule types first (critical and serious before moderate and minor). Each card explains how the issue can affect real tasks—forms, navigation, reading text—not just a rule name.

Fix these first

Up to five priority rule types (deduplicated by rule ID). Start here before reading every row in the full breakdown—guides open in plain language, with technical references optional.

  • criticalLikely quick fixOften content or front-end

    Empty buttons

    Why it matters

    Higher-severity items are more likely to block tasks or confuse assistive technology on this page.

    Ensure buttons have discernible text

    Buttons must have discernible text

    Open fix guide
    View technical details
  • criticalLikely quick fixOften content or front-end

    Missing alternative text on images

    Why it matters

    This affects people who rely on names and descriptions instead of visuals alone.

    Ensure <img> elements have alternative text or a role of none or presentation

    Images must have alternative text

    Open fix guide
    View technical details
  • seriousNeeds reviewContent & structure

    Ensure that text spacing set through style attributes can be adjusted with custom style…

    Why it matters

    This affects how people skim and navigate the page with assistive tech.

    Ensure that text spacing set through style attributes can be adjusted with custom stylesheets

    Inline text spacing must be adjustable with custom stylesheets

    Browse issue guides
    View technical details

    Rule ID: avoid-inline-spacing

    Axe / Deque rule reference →

  • seriousLikely quick fixOften design / visual

    Low color contrast

    Why it matters

    This can make text or controls harder to see for people with low vision or on bright screens.

    Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

    Elements must meet minimum color contrast ratio thresholds

    Open fix guide
    View technical details
  • seriousNeeds review

    Ensure every HTML document has a lang attribute

    Why it matters

    Higher-severity items are more likely to block tasks or confuse assistive technology on this page.

    Ensure every HTML document has a lang attribute

    <html> element must have a lang attribute

    Browse issue guides
    View technical details

    Rule ID: html-has-lang

    Axe / Deque rule reference →

Open full issue breakdown for every finding (9 rows), grouped by category.

What to do next

Follow this path to turn the report into real fixes, then confirm with a new scan—no account required.

  1. Fix the items above on real user paths

    Checkout, signup, contact, and main navigation matter more than obscure pages.

  2. Use our guides where they match

    Each “Open fix guide” links to a short article. Browse the issue library for more.

  3. Verify with quick manual checks

    Tab through forms and menus; note anything you cannot reach or operate without a mouse. Spot-check with zoom and your OS screen reader if you can.

  4. Run a fresh scan to see if the score moves

    Use Run a fresh scan below—each run gets its own link so you can compare before and after without logging in.

  5. Use a checklist for important launches

    Pre-launch accessibility checklist covers common gaps automation misses.

Keep improving over time

Fix repeated patterns (headers, cards, nav) before one-off pages. After updates, rescan and keep both report links to see what changed. One automated pass does not catch everything—use it as a structured starting point, not the final word.

Full issue breakdown

Every finding from this scan—open when you need the complete list.

See full issue breakdown

Findings are grouped by category when the scanner provides one. Fix higher severity items in each group first.

Other

Text & Typography

Color & Contrast

  • seriouscolor-contrast

    Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

    Elements must meet minimum color contrast ratio thresholds

Keyboard Navigation

Priority view (by severity buckets)

Grouped by automated severity. Each rule links to our issue guide when we have a match.

Critical

Blocks or severely harms access for some users—fix before release when possible.

High impact

Serious findings—often forms, names, or major contrast failures on key UI.

  • avoid-inline-spacingEnsure that text spacing set through style attributes can be adjusted with custom stylesheets Issue library →
  • color-contrastEnsure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Low color contrast
  • html-has-langEnsure every HTML document has a lang attribute Issue library →
  • link-nameEnsure links have discernible text Missing or vague link text

Lower priority

Moderate and minor rules—still worth fixing in templates to avoid repetition.

  • landmark-one-mainEnsure the document has a main landmark Issue library →
  • page-has-heading-oneEnsure that the page, or at least one of its frames contains a level-one heading Issue library →
  • regionEnsure all page content is contained by landmarks Issue library →

Pair fixes with the pre-launch checklist and WCAG in plain English.

Advanced details

Methodology, comparison, sharing, and caveats—open when you need them.

What this result means

Either many rules fired or the page was minimal. Use severity counts and categories below; confirm the worst issues manually with a keyboard.

Pre-launch checklist · What this tool does and does not do

How this compares

How this compares

This URL scored 28/100 on our automated summary. For orientation only, we show an illustrative blended average of 62/100 from sample public scans (not a live industry census). Your page is below that reference point (-34 points).

WCAG 2.1 Level AA is the conformance target most teams cite for policy. Automated scans surface many (not all) AA-related patterns; manual testing still covers context, state changes, and complex interactions.

State of Web Accessibility: methodology and trends

Related guides & articles
Limitations & legal context
Not legal or WCAG sign-off
This is an automated snapshot. Laws and standards are interpreted in context; use specialists when risk is high.
Why scores change between runs
Ads, A/B tests, and scripts can alter the page between visits.
Share, embed, or export

Share and embed

Link to this report or embed it on an internal wiki. The iframe loads the full public report; only use when the page is appropriate to share.

Link badge (HTML)

<a href="https://testaccessbility.com/report/sarhne-sarahah-pro-accessibility-report-60b67512" rel="noopener" style="display:inline-flex;align-items:center;gap:0.35rem;font:600 14px system-ui,sans-serif;color:#0f766e;text-decoration:none;border:1px solid #99f6e4;border-radius:9999px;padding:0.35rem 0.75rem;background:#f0fdfa">TestAccessibility: 28/100 · sarhne.sarahah.pro</a>

Markdown

[TestAccessibility score 28/100 — sarhne.sarahah.pro](https://testaccessbility.com/report/sarhne-sarahah-pro-accessibility-report-60b67512)

Embed (iframe)

<iframe src="https://testaccessbility.com/report/sarhne-sarahah-pro-accessibility-report-60b67512" title="Accessibility report for sarhne.sarahah.pro" width="100%" height="480" style="border:0;border-radius:8px;max-width:42rem" loading="lazy"></iframe>

Export

This public report already lists all violations above. Download a machine-readable snapshot, or use your browser's print dialog to save a PDF. Multi-format exports (PDF, Excel, CSV) with extra options are available from a completed scan in Free scan when signed in (audit view).

Similar scans

Similar scans

Other completed public scans on the same hostname or with a similar score.

Run a fresh scan

After you fix issues, scan the same URL again. Each run gets its own report link—keep both to see whether the score and severity counts improved.

No account required. High-traffic or template pages are good candidates to rescan first.

← Back to TestAccessibility