Digital Equipment Ltd.
A collaborative DEL team workspace with diverse people — backdrop for the accessibility statement
♿ WCAG 2.1 Level AA

Built for every kind of visitor

Digital Equipment Ltd. is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply relevant accessibility standards.

Standard
WCAG 2.1 Level AA — all 47 success criteria
Feedback response
Within 5 business days
Covers
Keyboard, screen readers, magnification, 200% zoom
Last updated
May 2026
Conformance status

WCAG 2.1 Level AA — the mandatory minimum

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the minimum standard for our website — measured through automated tooling, manual keyboard testing and periodic third-party audits.

Compliance is not a post-launch remediation task — it is a design and development constraint built into every decision, from typography to interaction patterns to ARIA implementation.

⭐ Level AAA criteria implemented where feasible

📅 Statement last updated: May 2026⏱ Response target: 5 business days

Measurable standards

4.5:1

Contrast — normal text

3:1

Contrast — large text

3:1

UI components & focus indicators

200%

Zoom — no horizontal scroll

≤3×/s

Flashing limit

CC

Captions on all video

✓

Announced form errors

✓

Colour never the only carrier of information

Ratios verified with WebAIM Contrast Checker and TPGi Colour Contrast Analyser.

In scope

  • All public-facing page templates
  • Partner Portal (authenticated area)
  • React islands — Solution Finder, Coverage Map, Product Comparison

Partial / best effort

  • Generated PDF documents — tagged structure
  • Third-party embedded content — best effort

Outside this scope

  • Admin interface — internal tool
  • Email templates — separate scope
The four principles (POUR)

What WCAG 2.1 AA means in practice

All 47 Level AA success criteria map to four foundational principles. Every page we ship is checked against them.

Perceivable

Information and UI must be presentable in ways users can perceive — alt text for non-text content, captions and transcripts for media, colour-independence (never colour alone), sufficient contrast, and text that resizes to 200% without clipping.

Operable

Every function works via keyboard with logical focus order and no traps, no seizure-triggering motion, generous time limits (portal session timeouts warn 2 minutes early and extend), and multiple ways to find content — menu, search, breadcrumbs, sitemap.

Understandable

Text is readable and predictable. Pages behave consistently, focus jumps sensibly, navigation repeats in the same order, and errors are described in plain language with suggested fixes.

Robust

Semantic HTML and ARIA landmarks that assistive technologies can reliably parse — validated with the screen readers and browsers our visitors actually use.

Accessibility measures

What we have implemented

The features below are live across the site today — not aspirations on a roadmap.

Keyboard navigation

All interactive elements are reachable and operable via keyboard alone.

Alt text

Descriptive alternative text for meaningful images throughout the site.

Colour contrast

Text and interface elements meet minimum contrast ratios.

Resizable text

Content remains functional and readable at 200% zoom.

Form labels

Clear labels and explicit error messages on every field.

Skip links

A skip-to-main-content link on every page.

Focus indicators

Visible focus states on every interactive element.

Semantic HTML

Proper heading structure, landmarks and landmark regions.

Compatibility

Tested with the tools you use

Our website is designed to be compatible with:

Screen readers

NVDA, JAWS and VoiceOver.

Speech recognition

Voice-control and dictation software.

Screen magnification

Magnification software and browser zoom.

Keyboard-only

Full navigation without a pointer device.

Bangla accessibility

Built বাংলা-first, not Bangla-as-an-afterthought

Bangla script demands more than translation — we tune typography to the script itself.

18px minimum body size

Bangla conjuncts (যুক্তবর্ণ), matra vowel marks and hasanta are taller and wider than Latin — at 16px they blur together, so our Bangla body text never ships below 18px.

Line-height 1.75

Bangla ascenders and the matra need more vertical room than Latin — 1.75 versus the 1.625 we use for English.

Screen-optimised font

A Bangla face hinted for Windows ClearType and macOS sub-pixel rendering, so conjuncts stay crisp at web sizes.

Screen-reader tested in Bangla

Labels, landmarks and announcements verified with Bangla screen-reader output — not just the English tree.

Why we do it

The Bangladesh context

There is no enforceable ADA/EN 301 549 equivalent here yet — we hold the line anyway.

Government procurement

Ministries are beginning to include accessibility in ICT specifications aligned with a2i guidelines — we are ready.

Diverse user base

Our clients’ staff span all ages and abilities, often on older equipment, low bandwidth and assistive technologies.

Machine readability

Semantic HTML and ARIA correlate directly with better search indexing and structured-data processing.

International clients

Multinationals evaluate accessibility as part of vendor assessment — proactive compliance is part of the offer.

Known limitations

Where we still fall short

Despite our best efforts, some content may not yet fully meet accessibility standards. We prefer to tell you plainly — including what we are doing about each gap and how to work around it today.

PDF documents

Some PDF documents — datasheets, brochures and older compliance papers — may not be fully accessible to screen readers, because they were produced before our accessible-document workflow.

  • Re-generating priority PDFs with tagged structure, reading order and text-based (non-scanned) content.
  • Need a document in an accessible format now? Email us and we will send the information as plain text or HTML within the 5-day target.

Third-party embedded content

Some embedded third-party content (maps, video players, portal widgets) sits outside our direct control and may not expose the same keyboard and screen-reader support as the rest of the site.

  • Auditing each embed and replacing or wrapping it with accessible alternatives where the vendor falls short.
  • If an embed blocks you, the same information is usually available on the linked page or from our desks directly.

Video captions

Some videos may not yet have captions, and most do not yet include audio description.

  • Captions are being added to every new video at publish time, and existing videos are being retrofitted in priority order.
  • A transcript or summary of any video is available on request via email.
Assessment approach

How we check — and enforce

  1. Automated testing tools

    Every page and template passes automated rule engines (axe-core) that catch structural violations — missing labels, contrast failures, broken landmarks — before anything reaches production.

  2. Manual keyboard navigation

    Real people walk every flow with the keyboard alone — menus, forms, modals, portals — verifying focus order, visibility and escape hatches that automation cannot judge.

  3. Periodic third-party audits

    Independent auditors re-assess the site against all 47 Level AA success criteria on a recurring cycle, so conformance is verified — not assumed.

Accessibility feedback

Hit a barrier? Tell us.

If you experience any accessibility barriers or have suggestions for improvement, reach the desk directly — we aim to respond within 5 business days.

⏱ Response target: 5 business days

Email
info@digitalequipment.com.bd
Phone
+880 1730-354850

What helps us fix it faster

  • The page address (URL) where you hit the barrier
  • The assistive technology and browser you were using
  • What you expected vs. what happened

What happens after you report

  1. Acknowledged within the 5-day target
  2. Triaged against WCAG criteria
  3. Fixed — or scheduled with an estimate
  4. You are told the outcome