Accessibility Statement — Daily Reality NG | March 2026
Accessibility Statement — Daily Reality NG
This page is honest about where Daily Reality NG currently stands on accessibility, what we are actively doing to improve, and what you can do right now if you encounter a barrier on this site.
⏱️ Check This Before You Read Further
If you are currently experiencing a barrier on this site — text that is difficult to read, images without descriptions, or anything that prevents you from accessing content — you do not need to read this entire page first. Go directly to our Contact Page and tell us the specific problem. We will respond and act on it. This statement tells you what we are doing and what we are not yet doing — the contact page is where you get direct help.
Takes 2 minutes. Could save you a frustrating experience trying to access content that should be available to everyone.
Welcome to Daily Reality NG — a platform built on the principle that real information should reach real people without unnecessary barriers. I write about Nigerian life, money, technology, law, and daily reality. That mission means nothing if a portion of my readers cannot access what I publish. This accessibility statement exists because I take that seriously — and because honesty matters more to me than presenting a polished image of something I have not yet fully achieved.
About This Statement
I am Samson Ese, the founder of Daily Reality NG. I launched this platform in October 2025 and have been building it independently since then. This accessibility statement was written personally by me based on real assessment of the site as it currently exists in March 2026. I have not used automated tools to generate a compliance claim — I have looked at what is actually here, what is missing, and what I am working on. That transparency is the only honest way to approach this.
📋 Table of Contents — Jump to Any Section
- Our Commitment to Accessibility
- Where We Currently Stand — Honest Assessment
- What Is Currently Working Well
- Known Gaps We Are Addressing
- WCAG 2.2 Compliance Status Table
- Technical Measures We Have Implemented
- Accessibility in the Nigerian Context
- How to Report an Accessibility Barrier
- Our Improvement Timeline
- Frequently Asked Questions
- Key Takeaways
♿ Our Commitment to Accessibility
Let me be direct about what this commitment actually is and is not. Daily Reality NG is a one-person publication built independently. I am not a large media organisation with a dedicated accessibility team, a budget for specialist audits, or engineers running automated compliance checks. What I am is a founder who believes that information created for Nigerians should reach Nigerians — all of them, including those who use screen readers, those with visual impairments, those on older devices, and those with cognitive or motor differences.
That commitment shows up in decisions I make every time I build a page. It shows up in the alt text I write for images. It shows up in the contrast ratios I enforce across every card and heading on this site. And it shows up in this statement — because publishing an honest account of where I am and where I am falling short is itself an accessibility practice. It tells readers exactly what they can and cannot expect, rather than hiding behind aspirational language.
What "commitment" actually means here
It means I prioritise accessibility in every new page I build. It means I fix barriers when they are reported. It means I do not dismiss accessibility as a concern only relevant to "big sites." And it means I am honest when something is not yet done rather than claiming compliance I have not verified. That is the standard I hold myself to. Not perfect — honest.
📊 Where We Currently Stand — Honest Assessment
Daily Reality NG is a growing blog hosted on Blogger, built and maintained solely by me since October 2025. As of March 2026, the site has over 630 published articles. The honest truth is that accessibility across 630+ articles is not uniformly perfect — some earlier articles were built before I had refined the current design standards, and those inconsistencies exist.
Here is what I can say honestly: every page built under my current Master Design Standard follows consistent contrast, alt text, readable font sizes, and mobile-first layout. Pages built before that standard was locked in — particularly from October to December 2025 — may have gaps that I am progressively working through.
⚠️ The honest reality of a solo publication
I have not paid for a formal third-party accessibility audit. I have not run automated WCAG compliance testing across every article. What I have done is build every new page to a defined standard that prioritises readability, contrast, and functional design — and I fix things when readers tell me something is broken. That is where I am. I am not pretending otherwise.
✅ What Is Currently Working Well
I want to be specific here, not vague. The following elements are consistently implemented across the current page architecture and all content produced under the V20 design standard:
Accessibility features confirmed present in current page builds
✅High contrast text: All body text is #1a1a1a on #ffffff — a contrast ratio of 15.8:1, well above WCAG AA minimum of 4.5:1. All headings are #000000 on white — 21:1 ratio. No faint grey text on white backgrounds exists in the current design standard. ✅Descriptive alt text on images: Every image published under the current standard includes specific, Nigerian-contextual alt text describing what is in the image rather than using generic phrases like "image" or leaving the field empty. ✅Semantic HTML structure: Pages use proper heading hierarchy — H1 for the main title, H2 for major sections, H3 for subsections. This means screen readers can navigate the structure of the page without needing to read every word. ✅Readable font sizes: Body text is a minimum of 16px across all pages, with 18px on key content sections. Line height is 1.8 for comfortable reading across devices. ✅Descriptive link text: Links use meaningful anchor text — "read our full guide on fintech safety" rather than "click here." This makes navigation meaningful for screen reader users who jump between links. ✅Mobile-first responsive design: Every page adapts correctly to screen widths from 375px upwards. No element requires horizontal scrolling on mobile except explicitly horizontal-scroll tables, which include swipe hints. ✅Keyboard navigation: All interactive elements — links, buttons, the back-to-top button, the share bar — are reachable and usable via keyboard navigation without requiring a mouse. ✅Image figcaptions: Every image has a figcaption that adds contextual meaning beyond the alt text — not just what the image shows but what it means in the context of the article. ✅No autoplay media: There is no audio or video content that plays automatically on any page. Readers control all media interactions. ✅No popup overlays or intrusive elements: Daily Reality NG has a permanent zero-popup policy. No modal, overlay, or any element blocks content or requires dismissal before reading. Pages load clean. ✅Static layout — zero animations: The entire site uses zero CSS animations, zero keyframes, zero floating elements, and zero JavaScript movement. This is a deliberate policy — animated content creates significant difficulties for readers with vestibular disorders, cognitive differences, or epilepsy. Every page renders instantly in a stable, static layout. ✅Adequate touch targets: All clickable elements are a minimum of 44x44px — meeting WCAG 2.2 target size requirements. This is particularly important for Nigerian readers using budget touchscreen Android devices.According to the World Health Organization, over 1 billion people worldwide live with some form of disability — approximately 13% of the global population. In Nigeria, the National Population Commission's 2006 census estimated approximately 3.6 million Nigerians with disabilities, a figure that researchers note significantly undercounts the actual number due to underreporting and social stigma around disability disclosure. Every design decision on this site is made with those readers in mind.
📎 Source: WHO World Report on Disability, 2011 | NPC Nigeria Census Data, 2006
⚠️ Known Gaps We Are Actively Addressing
This section is where I have to be honest in a way that most sites avoid. These are the things I know are not fully done. I am not hiding them. I am publishing them here because transparency about gaps is part of being a trustworthy publication.
Known accessibility gaps as of March 2026
⚠️Older articles (Oct–Dec 2025): Articles published in the first three months of the site's existence were built before the current design standard was defined. Some of these may have lower contrast values, missing or generic alt text, or structural inconsistencies. I am progressively updating these. ⚠️No formal WCAG audit completed: I have not commissioned a third-party accessibility audit. My compliance assessment is based on manual review and applying WCAG 2.2 principles to the design system — not automated testing across all 630+ pages. ⚠️No audio descriptions for complex tables: Some data tables on the site are complex enough that a screen reader user navigating purely by rows and columns may find the context difficult to follow without additional prose explanation. I am improving the setup paragraphs and follow-up analysis around every table to address this. ⚠️No dedicated screen reader testing: I have not tested the full site experience using NVDA, JAWS, or VoiceOver. The semantic HTML structure I use is designed to support these tools, but I cannot claim a fully tested screen reader experience until I have done that testing. ⚠️PDF and downloadable content: There are currently no PDF resources on the site. When I introduce downloadable resources in the future, I will ensure they meet PDF accessibility standards before publishing them. ❌No sign language video content: I do not currently produce video content, so sign language interpretation is not applicable. When I introduce video in the future, this will need to be considered. ❌No dedicated accessibility feedback form: Currently, accessibility issues are reported through the general contact page. A dedicated accessibility reporting route would be cleaner. I plan to add this as the site grows.📋 WCAG 2.2 Compliance Status — Current Assessment
The Web Content Accessibility Guidelines (WCAG) 2.2 are the internationally recognised standard for web accessibility, published by the W3C Web Accessibility Initiative. They are organised into three levels: A (minimum), AA (standard), and AAA (enhanced). Below is my honest self-assessment of where Daily Reality NG currently stands against key WCAG 2.2 success criteria for new content built under the V20 design standard.
| WCAG 2.2 Criterion | Level | What It Requires | Our Current Status | Notes for Nigerian Readers |
|---|---|---|---|---|
| 1.1.1 — Non-text Content | A | All images, icons, and graphics have text alternatives | ✅ Met — new content | Alt text on all current images. Older articles being updated progressively |
| 1.3.1 — Info and Relationships | A | Page structure communicated through proper HTML (headings, lists, tables) | ✅ Met | H1→H2→H3 hierarchy maintained. Tables use proper thead/tbody/tfoot |
| 1.4.3 — Contrast (Minimum) | AA | Text contrast ratio minimum 4.5:1 against background | ✅ Exceeded | #1a1a1a on #ffffff = 15.8:1. #000000 on #ffffff = 21:1. Both far exceed AA minimum |
| 1.4.4 — Resize Text | AA | Text can be resized to 200% without loss of content or function | ✅ Met | Fluid typography using clamp() and relative units responds correctly to browser text scaling |
| 1.4.10 — Reflow | AA | Content reflows at 320px width without horizontal scrolling (except where essential) | ✅ Met | All page content reflows at 375px and 320px. Only data tables require horizontal scroll, with explicit swipe hint |
| 1.4.12 — Text Spacing | AA | No loss of content when user adjusts letter/word/line spacing | ✅ Met | Layout uses flexible containers — spacing adjustments do not break readability |
| 2.1.1 — Keyboard | A | All functionality available via keyboard | ✅ Met | All links, buttons, and interactive elements reachable and operable via Tab and Enter |
| 2.4.3 — Focus Order | A | Focus order preserves meaning and operability | ✅ Met | Page structure follows natural reading order. No focus traps present |
| 2.4.4 — Link Purpose | A | Purpose of each link is clear from link text | ✅ Met | No "click here" links. All anchor text describes destination meaningfully |
| 2.4.11 — Focus Appearance | AA | Keyboard focus indicator is visible and meets minimum size | ⚠️ Partial | Browser default focus styles are visible. Custom focus styling not yet fully implemented across all elements |
| 2.5.8 — Target Size (Minimum) | AA | Click/touch targets minimum 24x24px (AA) — we aim for 44x44px | ✅ Exceeded | All tap targets are minimum 44x44px — critical for Nigerian users on small-screen budget Android phones |
| 3.1.1 — Language of Page | A | Default human language of each page is programmatically determined | ✅ Met | lang="en" set at document level on all pages via Blogger theme settings |
| 3.2.2 — On Input | A | Changing settings does not automatically cause unexpected context changes | ✅ Met | No dynamic form inputs or auto-submit elements exist on the site |
| 3.3.1 — Error Identification | A | If input errors occur, the item in error is identified and described | ⚠️ N/A currently | No custom forms currently on the site. Will be addressed when forms are introduced |
| 4.1.2 — Name, Role, Value | A | UI components have accessible names, roles, and states | ✅ Met — primary elements | Share buttons, navigation, and interactive elements include aria-label attributes. Complete audit ongoing |
| ⚠️ This is a self-assessment against WCAG 2.2 for content built under the V20 design standard as of March 2026. It is not a formal third-party audit. Older content published before the V20 standard may not meet all criteria above. We are progressively updating earlier content. Verify current WCAG 2.2 guidelines at w3.org/WAI. Self-assessment by Samson Ese, March 2026. | ||||
The honest reading of this table is that the current design standard meets or exceeds most Level A and Level AA criteria — particularly the ones that matter most for the Nigerian reader profile: contrast, mobile reflow, touch target size, and keyboard operability. The partial gaps are real and being addressed. The table does not lie in either direction.
⚙️ Technical Measures We Have Implemented
These are the specific technical decisions built into the Daily Reality NG design system — not aspirational statements but actual implemented choices:
🇳🇬 Accessibility in the Nigerian Context — What This Means Practically
Standard WCAG guidelines were written with a global audience in mind. But accessibility for Nigerian readers involves practical realities that international guidelines do not fully address. This section explains how I think about accessibility specifically within the Nigerian digital environment.
The accessibility dimensions that matter most for Nigerian readers in 2026
Data cost as an accessibility barrier: In March 2026, MTN Nigeria charges approximately ₦1,500–₦2,000 for a 1GB data bundle. A page that loads 5MB of uncompressed images is not just slow — it is expensive. For a Nigerian reader managing a limited data budget, a heavy page is an inaccessible page. Every image optimisation decision I make is, in part, an accessibility decision.
Device diversity: The majority of Daily Reality NG readers are on Android devices ranging from ₦40,000 budget phones with 2GB RAM to mid-range devices. The site must work on a Tecno Spark as reliably as it works on a Samsung Galaxy. This influences font size choices, touch target sizes, and layout decisions.
Network reliability: Intermittent 3G and 4G connections in many Nigerian cities and all rural areas mean that pages must load meaningfully even on slow or interrupted connections. Lazy loading, static layouts, and minimal JavaScript are accessibility measures for this context.
Screen reader users in Nigeria: Assistive technology adoption in Nigeria is growing, particularly as smartphones become primary computing devices. Readers who are blind or have low vision increasingly use TalkBack on Android. My semantic HTML structure, meaningful alt text, and descriptive link text are designed to support TalkBack and similar tools.
Cognitive load and readability: Plain language, short paragraphs, clear headings, and a predictable page structure reduce cognitive load for all readers — but particularly for those with dyslexia, ADHD, or cognitive processing differences. This is why every article follows a consistent structural pattern and why I enforce readable line heights and paragraph lengths.
The Web Accessibility Initiative of the W3C estimates that making websites accessible also improves overall usability for all users — not just those with disabilities. Accessible design choices like high contrast, clear navigation, and readable typography directly benefit Nigerian readers using phones in bright outdoor sunlight, readers with fatigue, and older readers experiencing age-related vision changes. Accessibility is not a niche concern — it is good design.
📎 Source: W3C Web Accessibility Initiative, Introduction to Web Accessibility, 2023 | w3.org/WAI
📬 How to Report an Accessibility Barrier
If you encounter anything on Daily Reality NG that creates a barrier for you — text you cannot read, images without descriptions that matter for the context, a layout that breaks on your device, or anything else — please tell me. This is not a formality. I read every message sent through the contact page and I act on real barrier reports.
How to report effectively — what to include
⚠️ Response time — honest expectation
Daily Reality NG is a one-person operation. I respond to all messages, but I do not have a 24-hour support commitment. My realistic response time is 2–5 business days. If you need content from a specific article that is currently inaccessible to you, mention that in your message and I will prioritise it.
📅 Our Accessibility Improvement Timeline
This is not a list of aspirations. These are specific things I am working toward, with honest assessments of where each one stands in March 2026.
| Improvement Area | What Specifically | Status | Target Period | Honest Reality Check |
|---|---|---|---|---|
| Older article alt text audit | Review and update alt text on articles published Oct–Dec 2025 where generic or missing | ⚙️ In Progress | Q2–Q3 2026 | 630+ articles means this is not a one-week job. I am working through oldest articles first |
| Custom focus indicators | Implement visible, styled keyboard focus rings across all interactive elements | 📋 Planned | Q2 2026 | Browser defaults are currently visible — custom styling improves this further |
| Screen reader testing | Full TalkBack and NVDA testing on key page types — homepage, article pages, static pages | 📋 Planned | Q3 2026 | Requires dedicated testing time. Semantic HTML already in place — testing will confirm and identify gaps |
| Dedicated accessibility contact route | Separate clearly labelled accessibility report pathway distinct from general contact | 📋 Planned | Q2 2026 | Low technical complexity — mainly a clarity and labelling improvement |
| Third-party accessibility audit | Commission an independent WCAG 2.2 audit once site revenue supports it | ⏳ Future | When viable | Professional audits cost money. The site is not currently monetised. This is a future goal tied to financial sustainability |
| Accessibility of future video content | Captions, transcripts, and audio descriptions on any video content published | 📋 Pre-planned | Before first video | No video content currently exists. These standards will be applied before any video is published |
| ⚠️ Timeline based on one-person operation capacity as of March 2026. Timelines may shift based on site growth and resource availability. This page will be updated when significant accessibility milestones are reached. Last reviewed: March 2026. | ||||
Disclosure
This accessibility statement was written personally by Samson Ese and reflects a genuine self-assessment of the site as it exists in March 2026. Daily Reality NG is not currently monetised. No products or services are promoted on this page. No affiliate links are present here. This is an honest public statement of accessibility status.
Disclaimer
This accessibility statement is provided for informational purposes and reflects a voluntary self-assessment. It is not a legal guarantee of full WCAG 2.2 compliance across all pages. The assessments described here apply primarily to content built under the V20 design standard. If you encounter an accessibility barrier not addressed by this statement, please report it directly via the contact page.
🎯 Key Takeaways — Accessibility Statement Summary
- Daily Reality NG is built by one person. This accessibility statement reflects honest self-assessment — not marketing language.
- All new content built under the V20 design standard meets or exceeds WCAG 2.2 Level AA on contrast, mobile responsiveness, touch target size, semantic structure, and keyboard navigation.
- The site enforces a permanent zero-animation policy — protecting readers with vestibular disorders, photosensitive epilepsy, and cognitive processing differences.
- Zero popups or overlays exist anywhere on the site. Content always loads clean without requiring dismissal of anything.
- Older articles (Oct–Dec 2025) are being progressively updated and may have accessibility gaps not present in newer content.
- A formal third-party WCAG audit has not been completed. Self-assessment is the current method of evaluation.
- Data cost, device diversity, and network reliability are treated as accessibility concerns specific to the Nigerian reader context — not just Western WCAG criteria.
- If you find an accessibility barrier, contact us at the contact page. We fix real barrier reports.
- Screen reader testing is planned for Q3 2026. Semantic HTML structure is already in place to support assistive technology.
- This page will be updated whenever significant accessibility improvements are completed. Last reviewed: March 2026.
📚 Related Articles on Daily Reality NG
❓ Frequently Asked Questions — Accessibility at Daily Reality NG
Is Daily Reality NG fully WCAG 2.2 compliant?
Not fully, and I am not going to claim otherwise. New content built under the V20 design standard meets or exceeds most Level A and Level AA criteria. However, older articles from October to December 2025 may have gaps, and I have not completed formal third-party verification across the entire site. What I can say is that the current design system prioritises accessibility in every decision and I fix barriers when they are reported.
Can I use a screen reader on this site?
Yes. The site uses semantic HTML5 throughout — proper heading hierarchy, meaningful link text, alt text on images, and correct table structure. These are the foundations that screen readers like TalkBack (Android), VoiceOver (iOS/macOS), and NVDA (Windows) need to navigate content. I have not yet completed formal screen reader testing, which is planned for Q3 2026. If you use a screen reader and encounter a specific problem, please report it via the contact page so I can address it.
Does Daily Reality NG work on older or budget Android phones?
Yes. The site is specifically designed for the Nigerian mobile reader profile — which includes devices ranging from ₦40,000 Tecno and Itel phones with 2GB RAM to mid-range Samsung and Infinix devices. The static layout, minimal JavaScript, lazy-loaded images, and mobile-responsive CSS all contribute to reliable performance on budget Android devices running Chrome or the Android system browser.
I use a lot of mobile data — is this site data-heavy?
I treat data consumption as an accessibility issue specific to the Nigerian context. All images beyond the hero image use lazy loading — they only download when you scroll to them. Hero images are compressed. The site has no autoplay video, no heavy JavaScript frameworks, and no ad networks loading third-party scripts that would balloon data usage. A typical article page should load the above-the-fold content in well under 1MB on a first visit.
Are there any flashing or moving elements on the site?
No. Daily Reality NG has a permanent zero-animation policy. There are no CSS animations, no JavaScript movement effects, no parallax scrolling, no flashing elements, and no content that moves after the page has loaded. Every page renders in a completely static layout. This is a deliberate decision that protects readers with photosensitive epilepsy, vestibular disorders, and attention or cognitive processing differences.
Can I navigate the site using only a keyboard?
Yes. All links, buttons, the back-to-top button, share bar buttons, and collapsible FAQ elements are reachable using Tab navigation and operable using Enter or Space. There are no focus traps. The natural reading order of the page follows the visual order. Browser default focus styles are visible — custom styled focus indicators are being implemented as part of our Q2 2026 accessibility improvements.
What if I find something that is not accessible?
Report it. Go to the contact page, describe the specific problem (which page, what went wrong, what device or assistive technology you use), and I will investigate it. Real barrier reports get real action — I do not log them and forget them. My realistic response time is 2–5 business days.
Is the Daily Reality NG newsletter accessible?
The newsletter is delivered through Kit (formerly ConvertKit) at dailyrealityngnews.kit.com. Kit's email platform produces plain-text compatible HTML emails with reasonable accessibility defaults. I write newsletter content with the same plain language, clear structure, and descriptive link text standards applied to the website. If you experience an issue with newsletter accessibility, please let me know via the contact page.
Does the site have a formal accessibility audit?
No. A professional third-party accessibility audit has not been completed. The site is not yet monetised and a formal audit is a future goal tied to financial sustainability. What currently exists is a consistently applied design standard built around WCAG 2.2 principles, applied manually to every page by the founder. This is not the same as a formal audit — and I am not pretending it is.
Will this accessibility statement be updated?
Yes. This statement was first published in March 2026 and will be updated whenever significant accessibility improvements are completed — after the screen reader testing in Q3 2026, after the older article audit is complete, and whenever other milestones from the improvement timeline are reached. The date at the top of this page reflects the last review date.
Thank you for reading this accessibility statement to the end. I know it is not the most exciting page on this site — it does not tell you how to save money or avoid a scam or understand a law. But it is one of the most honest pages here. I have told you exactly where Daily Reality NG stands on accessibility in March 2026 — what works, what doesn't, and what I am working on.
If there is a barrier on this site that prevents you from reading content you came here for, do not leave frustrated. Send me a message. That is the only way I know something needs fixing that I have not yet found myself.
— Samson Ese | Founder, Daily Reality NG
dailyrealityngnews.com | March 2026
© 2025–2026 Daily Reality NG — Empowering Everyday Nigerians | All posts are independently written and fact-checked by Samson Ese based on real experience and verified sources.
Comments
Post a Comment