Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DMobile Keyboard & AutofillAction2/2 eligible field(s) missing autocomplete or inputmodeFIX
F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FFavicon & BrandingAction1 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
CHeading HierarchyAction11 headings, 2 skip(s)REVIEW
- H1 Oman's First Platform for Smart Tenders and Services
- H6 Browse the latest public and private tenders across various sectors. skipped
- H1 Post Your Tender with Confidence on SafaQat duplicate H1
- H1 Tender Opportunities duplicate H1
- H6 Browse the latest public and private tenders across various sectors. skipped
- H2 تنفيذ كوفي بار
- H2 Wood, Aluminum,...
- H2 باب شتر
- H2 Shutter Doors �...
- H2 نقل أغراض من بركا...
- H2 Shift & Move Se...
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
BForm Accessibility2 of 2 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| (Enter your email address) | placeholder only | ||
| #g-recaptcha-response-100000 | textarea | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
Placeholder text disappears on focus and is not a reliable label.
<input type="email" name="email">
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
CLink & Button QualityAction12 issue(s) across 29 links and 23 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://services.omanair.com | Ministry of Transport, Communi… | new tab | Add '(opens in new tab)' to text |
| https://ithca.om/ | ithca group | new tab | Add '(opens in new tab)' to text |
| https://www.futurefund.om/FutureFund/Hom… | Oman Future Fund | new tab | Add '(opens in new tab)' to text |
| https://www.bankmuscat.com/en/Pages/defa… | Bank Muscat | new tab | Add '(opens in new tab)' to text |
| https://www.mara.gov.om/arabic/home.aspx | Ministry of Endowments and Rel… | new tab | Add '(opens in new tab)' to text |
| https://sme.gov.om/ | Riyada | new tab | Add '(opens in new tab)' to text |
| https://services.omanair.com | Ministry of Transport, Communi… | new tab | Add '(opens in new tab)' to text |
| https://ithca.om/ | ithca group | new tab | Add '(opens in new tab)' to text |
| https://www.futurefund.om/FutureFund/Hom… | Oman Future Fund | new tab | Add '(opens in new tab)' to text |
| https://www.bankmuscat.com/en/Pages/defa… | Bank Muscat | new tab | Add '(opens in new tab)' to text |
| https://www.mara.gov.om/arabic/home.aspx | Ministry of Endowments and Rel… | new tab | Add '(opens in new tab)' to text |
| https://sme.gov.om/ | Riyada | new tab | Add '(opens in new tab)' to text |
| /terms-and-conditions | Terms & Conditions | new tab | Add '(opens in new tab)' to text |
| /privacy-policy | Privacy Policy | new tab | Add '(opens in new tab)' to text |
| /payment-policy | Payment Processing Policy | new tab | Add '(opens in new tab)' to text |
| https://apps.apple.com/us/app/safaqat-ap… | app store | new tab | Add '(opens in new tab)' to text |
| https://play.google.com/store/apps/detai… | play store | new tab | Add '(opens in new tab)' to text |
| https://x.com/safaqat_om | x | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/@Safaqat_om | yt | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/safaqat_om/ | new tab | Add '(opens in new tab)' to text | |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Add '(opens in new tab)' to link text or aria-label.
https://services.omanair.com; https://ithca.om/; https://www.futurefund.om/FutureFund/Home; https://www.bankmuscat.com/en/Pages/default.aspx; https://www.mara.gov.om/arabic/home.aspx; https://sme.gov.om/; https://services.omanair.com; https://ithca.om/; https://www.futurefund.om/FutureFund/Home; https://www.bankmuscat.com/en/Pages/default.aspx (+10 more)
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button (#186 on page); button (#191 on page); button (#196 on page); button (#201 on page); button (#206 on page); button (#211 on page); button (#217 on page); button (#222 on page); button (#227 on page); button (#232 on page) (+2 more)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
CColor Contrast (Screenshot)Action20 text elements analyzed, 19 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Oman's First Platfor… | 1.44:1 | 3.0:1 | #000000 | #2B2827 | Fail |
| h1 Post Your Tender wit… | 2.75:1 | 3.0:1 | #000000 | #515454 | Fail |
| h1 Tender Opportunities | 2.68:1 | 3.0:1 | #000000 | #515251 | Fail |
| h2 تنفيذ كوفي … | 19.95:1 | 3.0:1 | #000000 | #F9F9F9 | Pass |
| h2 Wood, Aluminum,... | 2.89:1 | 3.0:1 | #000000 | #565756 | Fail |
| h2 باب شتر | 2.89:1 | 3.0:1 | #000000 | #565756 | Fail |
| h2 Shutter Doors �... | 2.89:1 | 3.0:1 | #000000 | #565756 | Fail |
| h2 نقل أغراض م… | 2.89:1 | 3.0:1 | #000000 | #565756 | Fail |
| h2 Shift & Move Se... | 2.89:1 | 3.0:1 | #000000 | #565756 | Fail |
| title SafaQat Tenders | Fi… | 2.97:1 | 4.5:1 | #000000 | #56595A | Fail |
| span safaqat | 2.97:1 | 4.5:1 | #000000 | #56595A | Fail |
| a Home | 2.98:1 | 4.5:1 | #000000 | #56595B | Fail |
| a About Us | 2.94:1 | 4.5:1 | #000000 | #56585A | Fail |
| a Tenders | 2.94:1 | 4.5:1 | #000000 | #56585A | Fail |
| a Products | 2.93:1 | 4.5:1 | #000000 | #55585A | Fail |
| a Our Suppliers | 2.93:1 | 4.5:1 | #000000 | #55585A | Fail |
| a Contact Us | 2.88:1 | 4.5:1 | #000000 | #545759 | Fail |
| button English | 2.88:1 | 4.5:1 | #000000 | #545758 | Fail |
| span Add Tender | 2.47:1 | 4.5:1 | #000000 | #4F4C4C | Fail |
| span Login | 1.88:1 | 4.5:1 | #000000 | #413A36 | 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.
ALandmark Structure5 landmarksPASS
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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
A+Heading Text Quality1 heading-text-quality issue(s) detectedPASS
A+Alt Text Quality1 of 33 images have issuesPASS
| Issue | Count |
|---|---|
| generic | 1 image(s) |
A+Form Input Types2 form control(s) checked, no type mismatchesPASS
A+Form Input Quality2 form control(s) checked, no input-semantic issuesPASS
A+Document LanguageLang attribute set to "en"PASS
A+Tabindex Anti-Patterns13 explicit tabindex attribute(s) checked, no anti-patternsPASS
AIframe Accessibility1/2 iframe(s) missing title; 0 placeholder(s)PASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 46 visible text node(s) render at >= 12 CSS pixelsPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Print StylesheetPrint styles detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Lighthouse Accessibility AuditsScore 98/100 — 1 failing, 23 passedPASS
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.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Browse the latest public and private tenders across various sectors. div.flex > div.flex > div.flex > h6.text-base |
Browse the latest public and private tenders across various sectors. div.min-h-screen > div.flex > div.w-full > h6.text-base |
These are opportunities to improve keyboard navigation in your application.