Welcome to Accessible Notes

Accessible Notes is a web app that transforms your documents — PDFs, scanned images, and more — into clean, editable text and exports them in formats that everyone can use. Whether you're working with a scanned research paper, a handwritten form, or a complex document with figures, Accessible Notes handles the heavy lifting so you can focus on the content itself.

The process is simple: upload a document, let the transcription engine read and structure it into markdown, review and edit the result in a clean editor, then export to PDF, Word (DOCX), HTML, or Markdown. Every exported format is built to meet accessibility standards — structured headings, proper reading order, and output that works well with screen readers and other assistive technologies.

Accessible Notes is designed from the ground up to be usable by everyone, including people who rely on assistive technologies. The app itself follows accessibility best practices, and the documents it produces carry that same commitment forward. You don't need to be a technical expert to get great results — the app guides you through every step.

If you're just getting started, every account starts with 30 free pages — no subscription needed. Sign in to get started.

What would you like to do?

• New here? Create an account and start with 30 free pages
• Upload and transcribe a document — learn about Notes and Transcription
• Review and edit figures — explore The Editor and Figures
• Export your work — see Exporting for PDF, DOCX, HTML, and Markdown options
• Check accessibility — read about Our Approach and Verifying Your Documents
• Manage your subscription — view Plans & Pricing

Getting Started

Getting into Accessible Notes takes just a minute. There's no traditional sign-up form to fill out — no username to choose, no password to create or remember. Instead, you sign in with a Google or Microsoft account you already have, and your Accessible Notes account is created automatically the first time you do.

Every account comes with 30 free pages — no subscription or payment needed. Use them at your own pace to try the full product. When you're ready for more, subscribe to the Individual plan for 100 pages per week.

If you've already signed in with one provider (say, Google) and later want to use the other (Microsoft), your accounts can be linked automatically as long as both use the same email address. See Account Linking for details.

• Creating Your Account
• Signing In with Google or Microsoft
• Account Linking

Creating Your Account

No password required

Accessible Notes doesn't use traditional email-and-password accounts. Instead, you sign in with an existing Google or Microsoft account. Your Accessible Notes account is created automatically the very first time you sign in — there's nothing extra to fill out.

How to get started

1. Go to the Accessible Notes sign-in page.
2. Click Sign in with Google or Sign in with Microsoft, whichever you prefer.
3. You'll be taken to Google or Microsoft to confirm the sign-in. They'll ask for permission to share basic profile information — your name and email address — with Accessible Notes.
4. Approve the request, and you're in. Your account is created and you're ready to go — your 30 free pages are available immediately.

That's it. You'll land directly in the app, ready to upload your first document.

Your free pages

• Every account starts with 30 free pages — no subscription or payment needed.
• You have full access to all features — PDF export, DOCX, HTML, transcription, figures, and accessibility checking.
• Free pages don't expire. Use them at your own pace.
• When you've used your free pages, subscribe to the Individual plan ($59/year) for 100 pages per week.

For details on available plans, see Plans & Pricing.

What information does Accessible Notes receive?

When you sign in with Google or Microsoft, Accessible Notes receives only your name and email address. This is used to identify your account. Accessible Notes does not receive your password or access to your email.

Switching providers later

If you sign up with Google and later want to use Microsoft (or vice versa), see Account Linking — as long as both accounts share the same email address, they'll be connected automatically.

Signing In with Google or Microsoft

How to sign in

1. Go to the Accessible Notes sign-in page.
2. Click Sign in with Google or Sign in with Microsoft.
3. You'll be redirected to Google or Microsoft, where you'll confirm which account you want to use.
4. Once you confirm, you're redirected back to Accessible Notes and signed in.

If this is your first time signing in, your account is created automatically at this step. See Creating Your Account for more on that.

Staying signed in

Once you're signed in, Accessible Notes keeps you logged in via a secure session cookie. You won't need to sign in again each time you visit — your session is maintained until you explicitly sign out or it expires naturally.

If you're working on a shared or public computer, it's a good idea to sign out when you're done. You can do this from your account menu.

Browser compatibility

Accessible Notes works on any modern browser, including recent versions of Chrome, Firefox, Safari, and Edge. No plugins or extensions are required.

Trouble signing in?

A few things to check if you run into problems:

• Make sure you're choosing the right provider. If you created your account with Google, sign in with Google. If you used Microsoft, use Microsoft. If you're not sure, try both — if the same email address is on both accounts, they may already be linked. See Account Linking.
• Check that cookies are enabled. Accessible Notes uses a session cookie to keep you logged in. If cookies are blocked, sign-in won't work.
• Try a different browser. If one browser is giving you trouble, another may work while you troubleshoot.

If you're still stuck, contact support.

If you need to change your email preferences or manage marketing communications, you can do so from your account settings.

Account Linking

What is account linking?

Accessible Notes supports signing in with either Google or Microsoft. If you have accounts with both providers that share the same email address, they are linked automatically — you can use either one to sign in to the same Accessible Notes account.

How it works

When you sign in, Accessible Notes identifies you by your email address. If you first sign in with Google using you@example.com, and later sign in with Microsoft using the same email address, the system recognizes that both sign-ins belong to the same person. Your accounts are linked automatically at that point.

From then on, you can use either Google or Microsoft to sign in — whichever is most convenient. Both will take you to the same account with the same notes, settings, and subscription.

What stays connected

Everything in your Accessible Notes account is tied to your account identity, not to a specific sign-in provider. That means:

• Your notes are all there, regardless of which provider you used to sign in.
• Your subscription carries over — your plan and billing history are attached to your account.
• Your settings remain the same.

Accounts with different email addresses

Automatic linking only works when both providers use the same email address. If your Google account uses one address and your Microsoft account uses a different one, they will be treated as separate Accessible Notes accounts.

If you're in that situation and need help consolidating, contact support.

Signing in after linking

Once your accounts are linked, you can sign in with either Google or Microsoft at any time. If you're not sure which provider you used originally, try both — if your email address matches, either one will work.

See Signing In for step-by-step sign-in instructions.

Notes

Notes are the heart of Accessible Notes. A note is your workspace for a document — it holds the files you upload, the transcribed text, and any figures extracted during transcription. Everything related to a piece of content lives in one place.

Working with a note follows a natural lifecycle: you create the note and upload your source documents, submit them for transcription, review and edit the resulting markdown in the editor, and finally export the finished document in the format you need. At any stage you can return, make changes, and re-export.

A note can hold multiple uploaded files — for example, several photos of handwritten pages, or a PDF alongside a scanned cover image. The transcribed content from all those files is combined into a single editable body. If the document contains figures — images, charts, molecular structures, or other visuals — those are extracted separately and appear on the Figures tab.

When you no longer need a note, you can archive it to keep your dashboard tidy. Archived notes aren't deleted — you can retrieve them any time.

• Creating & Organizing Notes
• The Editor

Creating & Organizing Notes

Creating a note

To create a new note, click the New Note button on your dashboard. You'll land on a draft screen where you can give your note a title and upload your source documents before submitting for transcription.

Every note starts with the title "Untitled." You can rename it at any time — just click the title field and type a new name. A descriptive title makes it easier to find your notes later, especially once your dashboard fills up.

Uploading documents

From the draft screen, you can upload one or more files to a note. Supported formats are PDF, JPEG, and PNG. You can mix file types — for example, a PDF of lecture slides alongside a photo of your handwritten notes.

Files are added in the order you upload them, and all of them contribute to a single transcribed body. See How Uploads Work for details on file size limits and how pages are counted.

What's inside a note

Once transcription is complete, a note contains three things:

• Source documents — the original files you uploaded, preserved exactly as you provided them
• Transcribed body — an editable markdown document generated from your uploads, which you work with in The Editor
• Figures — images extracted from your source documents during transcription, each with alt text and an optional caption, accessible from the Figures tab in the editor (see Figures)

Finding your notes

All your notes appear in a list on your dashboard, sorted by most recently updated. Each note shows its title, the date it was last modified, and its current status (for example, whether it's still processing or ready to edit).

Archiving notes

When a note is no longer active, you can archive it. Archiving hides the note from your main dashboard list — it doesn't delete anything. Your source files, transcribed content, and figures are all preserved.

If you need an archived note again, you can find it in your archive and restore it to your active list at any time.

The Editor

Overview

When you open a note that's been transcribed, you land in the editor. The editor is split into two panes side by side: a markdown editor on the left where you type, and a live preview on the right that updates as you work. Changes are saved automatically — there's no save button to click.

At the top of the editor are two tabs:

• Review / Edit Markdown — the split-pane editor view
• Figures — the figures extracted from your document

The markdown editor

The editor uses a professional code-editing interface with a dark theme and a monospace font, making it easy to read and write structured text. Standard markdown syntax applies: **bold**, *italic*, # Heading, and so on.

Auto-save: Your work is saved automatically as you type. After you pause for about one second, your changes are written. You don't need to do anything — just write.

Keyboard shortcuts: The editor supports standard shortcuts you may already know:

• Ctrl+Z (or Cmd+Z on Mac) — undo
• Ctrl+Y (or Cmd+Shift+Z) — redo
• Tab — indent the current line

The live preview

The right pane shows a rendered preview of your markdown. It refreshes automatically about a third of a second after you stop typing, so you can see formatted output without any manual action.

The preview supports several features beyond basic markdown:

Math formulas — Write LaTeX math and it renders automatically. Use $...$ for inline math (within a sentence) and $$...$$ for display math (centered on its own line). For example, $E = mc^2$ renders as a formatted equation.

Callout blocks — You can highlight important information using GitHub-style callout syntax:

> [!NOTE]
> Something worth knowing.

> [!TIP]
> A helpful suggestion.

> [!WARNING]
> Pay attention to this.

> [!IMPORTANT]
> Critical information.

> [!CAUTION]
> Proceed carefully.

These render as styled blocks in the preview. If you used Study Buddy mode during transcription, tutor tips and gap-filling notes will appear as [!TIP] and [!NOTE] callouts automatically.

Figures — If your document contained figures, they appear in the preview wherever you've placed a <figure slug="my-figure" /> tag. You can copy a figure's reference from the Figures tab and paste it into the markdown editor to position it in your note.

Security

Content in the preview is sanitized. Raw HTML and scripts are not rendered, which keeps things safe when working with documents from various sources.

Figures tab

Switching to the Figures tab shows all the figures extracted from your source documents during transcription. See Figures for details on working with them.

Uploads & Page Counts

Before Accessible Notes can transcribe a document, you upload it to a note. You can upload PDFs, JPEGs, and PNGs — photographs of handwritten pages work just as well as digital documents.

What to upload: Accessible Notes works best with academic content — handwritten lecture notes, problem sets, study guides, and similar materials. Avoid uploading documents that contain personal information like social security numbers, medical records, or financial data. Your documents are processed by third-party services and may be reviewed by our team to improve quality.

Every file you upload contributes to your weekly page count. The page count is how Accessible Notes measures usage: a multi-page PDF counts as its number of pages, and each image file counts as one page. Your plan includes a weekly allowance, and once you reach it, you can't submit new notes for transcription until the count resets.

• How Uploads Work
• Page Counts & Limits

How Uploads Work

Supported formats

Accessible Notes accepts three file types:

• PDF — any PDF document, including scanned PDFs
• JPEG — photos or scanned images in JPEG format
• PNG — photos or scanned images in PNG format

The maximum file size is 20 MB per file. If a file is larger than that, you'll need to reduce its size before uploading — most PDF tools and image editors can do this.

Uploading to a note

You upload files on the note draft screen, before submitting for transcription. You can add multiple files to a single note — for example, a PDF of slides and a few photos of your handwritten notes from the same lecture session.

Files are ordered by the position you add them. When transcription runs, the content from all your files is combined into a single markdown body in that order, so it helps to upload them in the sequence you want the final document to follow.

What happens after upload

Once you upload a file, it goes through an optimization pipeline in the background:

• Compression — files are compressed to reduce storage size and speed up viewing
• Thumbnail generation — small previews are generated so your files load quickly in the interface

This optimization happens automatically and doesn't affect transcription quality — the original file content is always used when your document is transcribed. You don't need to wait for optimization to finish before submitting for transcription.

How pages are counted

Page counts are used to track your weekly usage:

• PDFs — the page count is extracted automatically from the document. A 10-page PDF counts as 10 pages.
• Images (JPEG, PNG) — each image file counts as 1 page, regardless of its dimensions or content.

See Page Counts & Limits for details on your weekly allowance and what happens when you reach it.

Page Counts & Limits

How pages are counted

Every document you upload contributes to your weekly page count:

• PDFs — counted by the number of pages in the file. A 15-page PDF adds 15 to your count.
• Images (JPEG, PNG) — each image file counts as 1 page.

Page counts are recorded when you upload files, before transcription begins.

Weekly usage limits

Your weekly usage limit depends on your plan:

If you're using free pages (no subscription), there is no weekly limit — free pages are a lifetime allowance of 30 pages total.

When the limit resets

Your page count resets every Sunday at midnight UTC. At that point, your full weekly allowance becomes available again.

What happens when you reach your limit

Once you've used your weekly allowance, you won't be able to submit new notes for transcription until the count resets. The submit button will be unavailable, and you'll see a message indicating that your limit has been reached for the week.

Your existing notes are not affected. You can continue to:

• Read and edit notes you've already transcribed
• Export existing notes to PDF, DOCX, HTML, or Markdown
• Upload files to draft notes (they'll be ready to submit once your count resets)

The limit only applies to submitting new notes for transcription — everything else remains fully accessible.

Checking your usage

You can see your current weekly page count and remaining allowance from your dashboard or account settings. This updates each time you upload a new document.

Transcription

Transcription is the process of turning your uploaded documents into accessible, editable text. Accessible Notes uses a vision model to read your documents and produce clean, structured markdown that you can edit and export.

You have real control over how transcription works. Before submitting, you choose how the transcriber handles unclear writing, spelling mistakes, and factual errors: silently fix them, flag them for your review, or leave them as-is. You can also enable Study Buddy mode, which adds educational annotations — helpful context, defined terms, and filled-in reasoning steps — directly in your document.

When you're ready to submit, you choose between two processing speeds. Eco queues your transcription for batch processing, which takes up to a day but is great for work that isn't urgent. Rapid processes your note within a minute or two when you need results right away. Both produce the same quality output.

• Transcription Modes
• Speed Options: Eco vs Rapid

Transcription Modes

Before you submit a note for transcription, you configure how the transcriber handles content errors — mistakes in logic, calculation, or factual content. You also choose whether to enable Study Buddy, which enriches your notes with educational annotations.

Writing errors like misspellings, unclear handwriting, and grammatical mistakes are always corrected automatically. These surface-level fixes don't change the meaning of your content and are indistinguishable from OCR artifacts in most cases.

These settings are chosen once, on the upload screen, before transcription begins. After transcription completes, you can check which options were used by opening the note's details.

Handling content errors

This setting controls what happens when the transcriber identifies logical inconsistencies, factual mistakes, or reasoning errors in your document — especially in math and algebra.

Annotate (default) Errors are preserved and marked with inline callout blocks so you can review them. You'll see two severity levels:

• Warning — the transcriber suspects something is wrong but isn't certain
• Caution — the transcriber is confident this is an error

These callouts appear immediately after the problematic content, so you see the mistake first and then the explanation.

Correct Errors are silently corrected based on context. The output reads as if the writer got it right from the start. Choose this when you trust the transcriber's judgment and want a clean result without annotations.

Study Buddy

Study Buddy is enabled by default. It enriches your transcription with educational annotations that make notes easier to study from. When enabled, the transcriber goes beyond reading your document — it acts as a tutor, adding context and filling in gaps.

Study Buddy adds two kinds of annotations:

• Tips ([!TIP] callout blocks) — helpful context placed inline where it's most relevant. These define terms used without introduction, label key concepts and techniques the first time they appear, and provide brief explanations. For example, if your chemistry notes mention "Le Chatelier's principle" without defining it, Study Buddy adds a tip. The same goes for a history lecture that references "Westphalian sovereignty" or a math class that invokes "the chain rule."

• Bridging notes ([!NOTE] callout blocks) — fill in missing intermediate steps. If an algebraic derivation skips from one step to a result, a biology explanation glosses over a mechanism, or a logical argument assumes prior knowledge you might not have, Study Buddy inserts the missing steps so you can follow along.

Study Buddy works across subjects — math, science, humanities, social sciences, and anything else where notes benefit from added context.

Both types of annotation appear in the editor preview as styled callout blocks and are included in your exports.

You can toggle Study Buddy off on the upload screen if you prefer a clean transcription without annotations. You can also edit or remove any annotation after transcription — they're just regular callout blocks in your note's markdown.

Speed Options

When you submit a note for transcription, it is processed immediately using our standard pipeline. You can expect results in one to two minutes in most cases.

Eco processing — coming soon

We're building an Eco mode that will schedule your transcription during off-peak hours. You'll get the same quality results, but on a timeline of up to one day — a small choice that helps reduce peak demand on data centers when you don't need your documents right away.

Eco mode is not yet available. When it launches, you'll see a second option alongside the submit button on the upload screen.

How to submit

On the upload and draft screen, click Submit for transcription at the bottom. Your note will be processed right away.

Figures

When your document contains images, charts, molecular structures, or any other visual element, the transcription engine extracts each one as a figure — an image paired with alt text and an optional caption. Figures appear on the Figures tab in the editor, where you can review and refine them before exporting.

Each figure is referenced from your note body using a simple tag like <figure slug="my-figure" />. When you export, the tag is replaced with the actual image, complete with alt text and caption, in whatever format you're exporting to.

The Figures tab

When you open a note that's been transcribed, the editor has two tabs at the top: Review / Edit Markdown and Figures. Switching to the Figures tab shows all the figures extracted from your source documents.

The tab has two panels:

• Left panel — figure list. All figures in your note are listed here by slug, with a preview of the alt text below each name. Click any figure to select it.
• Right panel — editor. Shows the selected figure's image, along with fields for alt text, caption, and a reference you can copy into your note.

If no figures were detected during transcription, the panel will say so.

Editing a figure

Select a figure from the list to load it into the editor. From here you can:

Review the image. The extracted image is displayed at the top of the editor panel. This is what will appear in your exported document.

Edit the alt text. Alt text is a written description of the figure for people who use screen readers or other assistive technology. It should describe what the figure shows and why it matters — not just "figure 1" or "diagram." Good alt text lets someone who can't see the image understand the same information a sighted person gets from looking at it. Changes save automatically as you type.

Edit the caption (optional). The caption is a short visible label displayed below the figure in your exported document. If the original document had a label near the figure — like "Figure 3: Reaction mechanism" — the transcription engine may have captured it here. You can edit it or leave it blank.

Replacing an image

If the extracted image isn't right — perhaps it was cropped poorly or you have a better version — click the Replace image button below the image preview. You can upload a JPEG or PNG file as a replacement.

Referencing figures in your note

Each figure has a markdown reference shown at the bottom of the editor panel:

<figure slug="my-figure" />

Place this tag in your note body (in the markdown editor) wherever you want the figure to appear. You can copy the reference using the clipboard button next to it — no need to type it manually.

When you export, each <figure> tag is replaced with the rendered image, alt text, and caption in the appropriate format for your export type.

Deleting a figure

To delete a figure, select it in the list and click the Delete button in the top-right corner of the editor panel. Deleting a figure removes it from the list and also removes any references to it from your note body.

If you want to remove a figure from your exported document without deleting it entirely, delete the <figure slug="..." /> tag from your note body instead. The figure stays in your list but won't appear in exports.

Exporting

Once your note is ready, you can export it to PDF, Word (DOCX), HTML, or Markdown. Each format has different strengths — PDF is ideal for polished, read-only documents; Word works well when you or your collaborators need to make further edits; HTML is great for web distribution; and Markdown is the most portable option for use in other tools.

All four formats are designed with accessibility in mind. Proper heading structure, alt text for every figure, semantic markup, and tagged content are included automatically — you don't have to do anything special to get an accessible export. The work you put into your note (clear headings, figure alt text, well-structured content) carries through directly into the exported file.

You'll find the export options on the edit and review screen for your note. Each format has a button that triggers the export and downloads the file to your computer.

Before you export and share: review your document for accuracy. Automated transcription does its best, but you are responsible for making sure the content is correct before distributing it. For PDFs, use the PDF/UA checker in the note details panel to verify accessibility compliance — it only takes a few seconds.

The sections below cover what each format produces and anything you should know before using it.

• PDF
• Word (DOCX)
• HTML
• Markdown

PDF Export

PDF export produces a polished, typeset document suitable for archiving, printing, and formal submission. The output meets the PDF/A-4f standard — an archival-grade format that bundles accessibility requirements alongside long-term preservation guarantees.

What you get

• High-quality typesetting. Your note is rendered using LuaLaTeX via pandoc, the same toolchain used by academic publishers and technical writers. Text, spacing, and layout look professional without any configuration on your part.
• Embedded figures. Figures from your note are embedded as images in the PDF with their alt text attached, so they are accessible to screen readers.
• Rendered math. If your note contains mathematical notation, it renders as native LaTeX math — proper fractions, symbols, superscripts, and all.
• Accessible structure. The PDF includes document structure tags that enable screen reader navigation: headings, paragraphs, figures with alt text, lists, and tables are all tagged correctly.
• Self-contained file. PDF/A-4f requires that all fonts be embedded in the file, so it will look consistent on any device — no dependency on fonts being installed.

Best uses

PDF works best when you want a document that:

• Won't be edited further after distribution
• Needs to look consistent across all devices and printers
• Should meet archival or formal submission requirements
• Contains math or figures that need to render precisely

Accessibility compliance

PDF/A-4f incorporates the PDF/UA (Universal Accessibility) standard, which covers the technical requirements for screen reader compatibility. This includes tagged content structure, alt text for images, reading order, and embedded metadata.

You can verify the accessibility of your exported PDF using our free PDF Checker — no login required. See Verifying Your Documents for details.

Word (DOCX) Export

Word export produces a .docx file that opens in Microsoft Word, Google Docs, LibreOffice, and any other application that supports the standard Office format. It's the recommended export format for most users — you'll see it marked with a star in the export panel.

What you get

• Proper heading structure. Headings from your note are mapped to Word's built-in heading styles (Heading 1, Heading 2, etc.), which enables the navigation pane, table of contents generation, and correct screen reader behavior.
• Figures with alt text. Each figure is embedded as an image with its alt text attached, so it remains accessible.
• Math notation. Mathematical expressions from your note are included in the document. Depending on what you need to do with them, you may want a tool like MathType to edit them after export.
• Editable content. Unlike PDF, a DOCX file is fully editable — useful when you need to make final adjustments, add institution-specific formatting, or collaborate with someone who prefers Word.

Best uses

DOCX works best when you want a document that:

• Will be edited after export, either by you or a collaborator
• Needs to be submitted to a system or institution that requires Word format
• Should serve as a starting draft for a longer document
• Will be shared with someone who works primarily in Word or Google Docs

Checking accessibility in Word

After exporting, you can verify the document's accessibility directly in Microsoft Word:

1. Open the exported .docx file in Word
2. Go to Review in the top menu, then click Check Accessibility
   • Alternatively: File → Info → Check for Issues → Check Accessibility
3. If Word prompts you to upgrade the document format, accept this — it's required to enable the full accessibility checker
4. Review the results panel, which lists any issues found along with suggestions for fixing them

Common things the checker looks for include missing alt text, reading order problems, and missing document title. Items flagged from an Accessible Notes export should be rare — if you find recurring issues, that's useful feedback for us.

If you need to fix an alt text issue, it's best to update it in Accessible Notes and re-export rather than editing it directly in the Word file. That way the fix applies to all your exports.

HTML Export

HTML export produces a single .html file with clean, semantic markup. It's a good choice for distributing documents on the web, embedding content in a website, or sending a file that anyone can open in a browser without installing anything.

What you get

• Semantic HTML5. Headings, paragraphs, lists, figures, and tables use the appropriate HTML elements — not just styled <div> blocks. This benefits both accessibility tools and anyone who processes the HTML further.
• Figures with alt text. Each figure is embedded as an image wrapped in a <figure> element, with your alt text attached. The HTML file is fully self-contained.
• ARIA attributes. Key elements include ARIA roles and labels where they help screen reader users understand the document structure.
• Clean output. The HTML is readable and suitable for further processing, styling with your own CSS, or importing into a content management system.

Math formulas and MathJax

If your note contains mathematical notation, the exported HTML includes a reference to MathJax — a JavaScript library that renders LaTeX math notation in the browser. You'll see a <script> tag near the bottom of the file that loads it from a CDN. This is normal and expected — it's what makes formulas like $E = mc^2$ display as properly formatted math instead of raw text.

MathJax loads automatically when someone opens the HTML file in a browser. No setup is needed on your part.

If you're embedding the exported HTML into a website that already loads MathJax or KaTeX, you can safely remove the duplicate <script> tag to avoid loading it twice.

Best uses

HTML works best when you want a document that:

• Will be published on a website or shared as a web link
• Should be accessible in any browser without special software
• Needs to be integrated into a larger web project or CMS
• Will be processed further by scripts or other tools

Markdown Export

Markdown export produces a .md file containing your note's content in plain text markdown format. It's the most portable of all the export options — a markdown file opens in virtually any text editor, note-taking app, or version control system.

What makes this different from copying the editor

You might wonder: why export to Markdown when you can just copy the text from the editor? The key difference is figures.

In the editor, figures appear as tags like <figure slug="my-figure" />. These are specific to Accessible Notes — another app won't know what to do with them.

In the Markdown export, every figure tag is replaced with the actual image wrapped in a <figure> element with your alt text and caption:

<figure>
  <img src="data:image/png;base64,..." alt="Description of the figure" />
  <figcaption>Visible caption</figcaption>
</figure>

This means the exported file contains your complete document — content and visuals together — in a format that works anywhere that supports markdown with embedded HTML.

What you get

• Figures embedded as images. Each figure tag is replaced with an embedded image, alt text, and caption.
• Math notation preserved. Mathematical expressions stay in LaTeX format ($...$ for inline, $$...$$ for display). Apps like Obsidian, Typora, and many others render these natively.
• Callout blocks in GitHub-style syntax. Notes, warnings, and tips from your document use the widely-supported GitHub syntax:

  > [!NOTE]
  > This is an informational note.
  

• No proprietary syntax. The output is standard markdown — no Accessible Notes-specific placeholders remain.

Best uses

Markdown works best when you want a document that:

• Will be used in another markdown-based tool (Obsidian, Notion, Typora, Bear, etc.)
• Should be stored in version control alongside code or other text files
• Needs to be portable and readable without special software
• Will be processed by scripts, static site generators, or documentation tools

Accessibility

Accessibility is at the heart of everything Accessible Notes does. The app exists to make it easier to produce documents that work for everyone — including people who use screen readers, magnification software, refreshable braille displays, or other assistive technologies.

Rather than treating accessibility as a checklist to complete at the end, it's built into the processing pipeline from the start. Every export format includes proper semantic structure, alt text for figures, tagged content for screen reader navigation, and correct heading hierarchy. You get accessible documents by default, without needing to understand the technical details of each format's accessibility requirements.

Your role in this is straightforward: write clear, well-structured notes and provide meaningful alt text for your figures. The app handles the rest — translating your content into the appropriate accessibility structures for each export format.

Your responsibility before sharing

Accessible Notes does its best to produce accurate, well-structured documents — but automated transcription is not perfect. You are responsible for reviewing and editing your documents for accuracy before sharing them. Read through the transcription, correct any errors, and make sure the content says what you intend. This is especially important for math, science, and any content where a small mistake changes the meaning.

You should also verify accessibility before distributing. The PDF/UA checker in the note details panel lets you validate your PDF export against accessibility standards. Run it before sharing a document — it takes seconds and catches issues that are easy to miss.

The sections below explain how we approach accessibility in our exports and how you can verify that your documents meet standards before distributing them.

• Our Approach
• Accessibility Features
• Dyslexic-Friendly Font
• Verifying Your Documents

Our Approach

Accessible Notes is built around a simple idea: accessible documents should be the default, not an extra step. Every choice in the processing pipeline — from how your uploads are transcribed to how each export format is generated — is made with accessibility in mind.

What every export includes

Regardless of which format you export to, your document will contain:

Proper heading hierarchy. Headings flow from H1 down through H2, H3, and so on, without skipping levels. This matters because screen reader users navigate documents by jumping between headings — a consistent hierarchy makes that navigation predictable and efficient.

Alt text for all figures. The alt text you write in the Figures tab is embedded in every export format. A person using a screen reader will hear your description read aloud in place of the figure.

Semantic markup. Lists are real lists, tables are real tables, figures are real figures. This gives assistive technology the information it needs to convey structure, not just visual appearance.

Tagged/structured content. In formats that support it (PDF and DOCX in particular), content is tagged so that screen readers can navigate by section, identify reading order, and understand the role of each element.

Format-specific accessibility

PDF — Exports meet the PDF/A-4f standard, which incorporates PDF/UA (Universal Accessibility). Fonts are embedded, document structure tags are included, and figures are embedded as images with alt text.

Word (DOCX) — Headings use Word's built-in heading styles, which enable the navigation pane and proper screen reader behavior. Figures are embedded as images with alt text set on the image object itself.

HTML — Output uses semantic HTML5 elements with ARIA attributes where helpful. Figures are wrapped in <figure> elements with alt text and captions. The document structure is readable by browser accessibility tools.

Markdown — Headings follow a consistent hierarchy. Figures are wrapped in <figure> elements with images, alt text, and captions. Callout blocks use the GitHub-style syntax that most markdown renderers understand.

How transcription supports accessibility

The transcription engine is specifically configured to produce accessible output:

• Heading levels are structured logically, not just based on visual size in the original
• Figure alt text is generated as a starting point — always review and refine it before exporting
• Math notation is formatted as standard LaTeX that renders correctly in all export formats
• Content structure (lists, tables, callouts) is preserved or inferred from the original layout

Auto-generated alt text is a draft, not a final answer. Read each figure description and ask whether someone who couldn't see the figure would understand what it shows. If not, update it before exporting.

Accessibility Features

This page summarizes the accessibility features built into the Accessible Notes app itself — the editor, navigation, and supporting screens you use day to day. For information about the accessibility of the documents you export, see Our Approach. For the formal Section 508 / WCAG 2.1 conformance report, see the VPAT.

Keyboard support

Every interactive control in the app can be operated from the keyboard alone — no pointer required. That includes buttons, menus, form fields, the figure metadata editor, the list reorder control, and dialog windows.

• Tab / Shift+Tab — move focus between controls in the order they appear on the page.
• Enter / Space — activate the focused button, link, or checkbox.
• Arrow keys — move within composite widgets such as the figure editor and the reorder list.
• Escape — close the open dialog and return focus to the control that opened it.
• A skip link appears as the first focusable element on every page, letting keyboard users jump straight to the main content past the navigation.

The app does not define any single-character keyboard shortcuts that would compete with assistive-technology shortcuts; all command-style shortcuts use a modifier key.

Visible focus indicators

When you Tab through the page, the control that has focus is outlined with a high-contrast ring so you can see exactly where you are. This works in both the light and dark themes.

Screen-reader semantics

The interface uses native HTML semantics throughout:

• Landmark regions — the navigation, main content, and sidebar are wrapped in <nav>, <main>, and <aside> so that screen-reader users can jump between regions with a single keystroke.
• Form labels — every input is associated with a visible label, and validation errors are announced through ARIA live regions when they appear.
• Dialog roles — modal dialogs use role="dialog" with a labelled title, focus moves into the dialog on open, and focus returns to the invoking control on close.
• Status updates — long-running tasks (transcription, export rendering) post their progress to a polite live region so screen readers announce progress without interrupting whatever the user is doing.

Decorative icons are hidden from assistive technology with aria-hidden, so screen readers don't announce a UI flourish as if it were a separate element.

Authoring prompts for accessibility

The editor surfaces accessibility prompts at the points where they matter:

• Alt text is a required field in the figure editor. You can't save a figure without describing it, so exports never silently lose alt text at the figure level.
• The audit panel in the editor sidebar lists figures that still need attention and document-level structural issues (missing top-level heading, untitled note, etc.) with actionable remediation guidance.
• Heading-level prompts appear when you create headings that would skip a level.

This authoring-side enforcement is what lets the export pipeline produce tagged PDF/UA-1, accessible DOCX, and semantic HTML by default.

Themes and contrast

Both the light and dark themes use a curated palette in OKLCH (a perceptually-uniform color space) with body text, brand text, and error states tuned to meet the 4.5:1 minimum contrast ratio for normal text required by WCAG 2.1 AA.

You can switch themes from the user menu in the top right. The choice is saved per user.

Dyslexic-friendly font

Each note has its own Dyslexic-friendly font toggle that switches the live preview and PDF/HTML exports to OpenDyslexic.

Resize and reflow

All app text is sized in relative units, and layout containers reflow at narrow viewports:

• Browser zoom up to 200% — content stays readable without horizontal scrolling.
• 320 CSS-pixel viewport — the layout collapses to a single column with no two-dimensional scrolling.

This means the app works on small screens, on a desktop with the browser zoomed in, and on a screen with the operating-system display scale increased.

Document export accessibility

Documents you export carry their accessibility metadata with them:

• PDF — tagged structure with PDF/UA-1 conformance metadata, embedded fonts, alt text on figures, and a declared document language. See PDF Export.
• Word (DOCX) — headings use Word's built-in heading styles, figures carry alt text on the image object, and the document language is set in the file metadata.
• HTML — semantic HTML5 with ARIA where helpful, <figure> and <figcaption> for images, and a lang attribute on the root element.
• Markdown — headings follow a consistent hierarchy and figures use HTML <figure> blocks so alt text and captions survive most renderers.

You can verify a PDF against PDF/UA from the note details panel before sharing it.

Compatibility

Accessible Notes is built and tested with the following browsers and assistive-technology pairings, current versions:

• Browsers — Chrome, Firefox, Safari, Edge.
• Screen readers — NVDA and JAWS on Windows, VoiceOver on macOS, VoiceOver on iOS, TalkBack on Android.
• Magnification — operating-system zoom and browser zoom up to 200%.
• Voice control — Voice Control on macOS and iOS, Voice Access on Windows.

Older browser versions and older AT versions may work but are not part of the test matrix.

Known limitations

We try to be honest about gaps. The current limitations are documented in the formal VPAT; the most user-visible ones:

• Billing checkout is delivered through a third-party iframe (Paddle). You can close the overlay with Escape, but focus management inside the iframe is governed by Paddle's SDK rather than by Accessible Notes.
• Export accessibility checks run on a representative sample in CI rather than on every individual export. Use the PDF/UA checker on the export itself if you need per-document confirmation.

Reporting accessibility issues

If you hit something that doesn't work for you with assistive technology, we want to hear about it. Email support@accessiblenotes.com with:

• the page or feature you were using,
• the assistive technology and browser,
• and what you expected to happen.

We treat accessibility regressions as bugs, not feature requests.

Dyslexic-Friendly Font

Each note has a Dyslexic-friendly font toggle in the editor title bar. When enabled, the note's live preview and most export formats render in OpenDyslexic — a typeface designed to increase readability for people with dyslexia. The wider letter shapes and weighted bottoms help reduce the visual confusion that standard typefaces can cause.

What changes

• Live preview — the markdown preview pane switches to OpenDyslexic immediately.
• PDF export — the font is embedded directly in the PDF, so it displays correctly on any device without requiring the reader to have the font installed.
• HTML export — the exported HTML references OpenDyslexic via a web font, so it loads automatically in any modern browser.
• Markdown export — unaffected, since Markdown is plain text with no font information.
• Word (DOCX) export — the document's style references are set to OpenDyslexic. If the reader has the font installed, Word will use it; otherwise Word falls back to its default font. This is a limitation of the DOCX format — fonts cannot be embedded the way they can in PDF.

How to use it

1. Open a note in the editor.
2. Check the Dyslexic-friendly font checkbox in the title bar (next to the note title).
3. The preview updates immediately. Exports generated while the toggle is on will use the dyslexic-friendly font.

The setting is saved per note, so you can enable it for some notes and leave others in the default font (Lato). Toggling the font also invalidates any cached exports, so the next export will always reflect the current setting.

Verifying Your Documents

Exporting an accessible document is only half the job — verifying it is the other half. Each format has its own tools for checking accessibility, and it's worth running a check before you distribute your work.

PDF — use the free PDF Checker

Accessible Notes provides a free PDF Checker tool. No login required.

How to use it:

1. Go to PDF Checker
2. Upload any PDF file
3. Get an instant accessibility compliance report

The checker runs your PDF through veraPDF, an industry-standard open-source validator, and tests it against PDF/UA-1 standards. The report shows:

• Overall compliance status — pass or fail
• Specific rule violations — each issue is listed with a description of what the rule requires and what was found

The tool works on any PDF, not just exports from Accessible Notes. If you receive a PDF from someone else and want to check whether it's accessible, you can use it for that too.

If the checker reports issues on an Accessible Notes export, that's a bug we want to know about. Our exports are designed to be fully compliant, so any failure points to something that needs fixing on our end.

Word (DOCX) — use Word's built-in checker

Microsoft Word includes an accessibility checker that evaluates your document and lists any problems it finds.

How to run it:

1. Open the exported .docx file in Microsoft Word
2. Go to Review in the top menu, then click Check Accessibility
   • Alternatively: File → Info → Check for Issues → Check Accessibility
3. If Word prompts you to upgrade the document format, accept this — upgrading enables the full accessibility checker
4. The Accessibility panel opens on the right, listing issues grouped by severity

What the checker looks for:

• Missing or empty alt text on images
• Reading order problems
• Missing document title
• Tables without header rows
• Color contrast issues (if applicable)

If you find alt text issues, fix them at the source — update the alt text in Accessible Notes and re-export. Editing alt text directly in the Word file is possible but means your fix won't carry over if you export again.

HTML — use browser tools or online validators

Several free tools can check the accessibility of an HTML file:

Browser accessibility inspector:

• Open your HTML file in Chrome or Firefox
• Press F12 to open developer tools
• Look for the Accessibility tab (in Chrome) or the Accessibility tree in Firefox's Inspector

WAVE (Web Accessibility Evaluation Tool):

• Go to wave.webaim.org
• You can paste your HTML directly or use the browser extension to evaluate a page

axe DevTools:

• Install the axe DevTools browser extension
• Open your HTML file in a browser, then run axe from the extension panel
• Gets detailed results mapped to WCAG criteria

General tips

Verify before distributing. It takes a few minutes and can save your readers from significant frustration.

Fix at the source. If you find accessibility issues — especially missing or inadequate alt text — update them in Accessible Notes and re-export rather than patching the exported file. Changes made directly to a PDF or DOCX won't carry over next time you export.

Figure alt text is the most common gap. Auto-generated alt text is a starting point. Before exporting, review each figure's alt text and make sure it actually describes what the figure shows. See Figures for guidance on editing alt text.

Subscriptions

Accessible Notes offers the Individual plan at $59/year and Team plans at $79/seat/year. Every plan includes every feature the app offers. Each account starts with 30 free pages — no subscription needed to get started.

Billing is handled securely by Paddle, a trusted payment processor used by software products worldwide. You can manage your subscription, view billing history, and make changes directly from your account settings.

• Plans & Pricing
• Canceling

Plans & Pricing

Free pages

Every Accessible Notes account starts with 30 free pages — no subscription or payment needed. Use them at your own pace to try the full product. Free pages don't expire.

Plans

Both plans are billed annually. There is no monthly billing option.

What's included

Every plan includes every feature Accessible Notes offers:

• Upload and automated transcription of PDFs and scanned images
• Markdown editor for reviewing and editing transcribed content
• Figure support
• Export to accessible PDF, Word (DOCX), HTML, and Markdown
• Accessibility checking
• Dyslexic-friendly exports

The Team plan adds multi-seat management, invoiced billing, and purchase orders.

Weekly usage limit

Your usage limit resets every week at midnight UTC on Sunday. Pages are counted based on the documents you process — each page of a document counts as one page toward your limit.

If you reach your weekly limit before the reset, you'll need to wait until Sunday midnight UTC for it to refresh.

Your existing notes and exports remain fully accessible when you hit your limit — the usage limit only affects submitting new documents for transcription.

Team plan usage

On Team plans, each team member gets their own independent usage limit of 200 pages per week. Usage limits do not pool or stack across team members.

Refund policy

If you're not satisfied, Accessible Notes offers a 30-day refund policy on any payment, no questions asked. Contact support to request a refund.

Annual billing

All subscriptions are billed once per year. You won't be charged monthly. Your billing date is set when you first subscribe, and you'll be charged on the same date each year when your subscription renews.

Canceling

How to cancel

You can cancel your subscription at any time from your account settings. There are no hoops to jump through — the option is right there in your account.

What happens when you cancel

Cancellation is not immediate. When you cancel:

• Your subscription is scheduled to end at the close of your current billing period.
• You keep full access to Accessible Notes — including processing new documents — until that date.
• You won't be charged again after the period ends.

Changing your mind

If you cancel and then decide you want to keep your subscription, you can undo the cancellation before your billing period ends. Your subscription will continue as normal and you won't lose any time you've already paid for.

After your subscription ends

Once your subscription period ends:

• Your notes remain accessible. You can still read and export documents you've already processed.
• Free pages may still be available. If you haven't used all 30 of your lifetime free pages, you can continue processing documents until they run out.
• Otherwise, subscribe again to continue. Your existing notes will still be there when you come back.

If you resubscribe later, you'll subscribe to the Individual plan and pick up where you left off. Your existing notes will still be there.

Refunds

Accessible Notes has a 30-day refund policy on any payment. If you've been charged within the last 30 days — whether for a new subscription or a renewal — you can request a full refund on that charge. Contact support and we'll process it promptly, no questions asked.

Refunds are processed through Paddle and typically appear on your bank statement within 5-10 business days as a credit from PADDLE.NET* ACC NOTES.

Something else going on?

If you're canceling because of a specific problem or because something isn't working the way you expected, support is happy to help. Sometimes an issue can be resolved without needing to cancel at all.

Legal

Legal documents governing the use of AccessibleNotes.

• Privacy Policy — how we collect, use, and protect your data
• Terms of Service — the agreement governing your use of AccessibleNotes
• Accessibility Statement — our commitment to digital accessibility

Privacy Policy

Last updated: April 1, 2026

Introduction

Normal Thought Technologies LLC ("we", "our", "us") operates AccessibleNotes. We are committed to protecting your privacy. This policy explains what data we collect, how we use it, and your rights.

What Data We Collect

Account Information

When you create an account, we collect your email address and password (stored as a secure hash — we never store your actual password).

Uploaded Documents

When you use our service, you upload images of handwritten notes and scanned documents for processing. We store these files temporarily to perform the conversion.

Usage Data

We collect basic usage data such as pages visited, features used, and error logs to improve the service.

How We Use Your Data

Document Processing

Your uploaded documents are sent to third-party AI services (Google Gemini and Anthropic Claude) for transcription. These services process your document images to extract text content. We do not control how these third-party services handle data beyond their published privacy policies:

• Google Privacy Policy
• Anthropic Privacy Policy

Quality Assurance and Product Improvement

We may review uploaded documents and generated outputs — both through automated systems and authorized staff — to evaluate and improve the accuracy and quality of our service. These reviews help us identify transcription errors, refine our processing pipeline, and develop better features. We do not sell or share your content with third parties for their own purposes.

Service Operation

We use your account information to authenticate you and provide the service. Usage data helps us identify and fix bugs and improve performance.

Data Retention

• Account data is retained as long as your account is active. You can delete your account at any time.
• Uploaded documents and generated outputs are retained while associated with your account. Deleting a note removes both the original upload and all generated files.
• Usage logs are retained for up to 90 days.

Content Suitability

AccessibleNotes is designed for academic content: lecture notes, problem sets, study materials, and similar documents whose output is intended to be shared. Because we review content for quality assurance and your documents are processed by third-party AI services, you should not upload documents containing personally identifiable information (PII), protected health information (PHI), financial records, or other sensitive personal data.

Third-Party Services

We use the following third-party services:

• Paddle — payment processing. Paddle acts as the Merchant of Record and handles all billing data. See Paddle's Privacy Policy.
• Google Gemini — AI-powered document transcription.
• Anthropic Claude — AI-powered document transcription.

Cookies

We use essential cookies for session management and authentication. We do not use tracking or advertising cookies.

Your Rights

You have the right to:

• Access your personal data
• Correct inaccurate data
• Delete your account and associated data
• Export your data

To exercise these rights, contact us at the email below.

Contact

For privacy-related questions, contact us at privacy@normalthought.com.

Changes to This Policy

We may update this policy from time to time. We will notify registered users of material changes via email.

Terms of Service

Last updated: April 1, 2026

Acceptance of Terms

These Terms of Service are a legal agreement between you and Normal Thought Technologies LLC ("we", "our", "us"), the operator of AccessibleNotes. By accessing or using AccessibleNotes, you agree to be bound by these terms. If you do not agree, do not use the service.

Service Description

AccessibleNotes converts handwritten notes and scanned documents into accessible digital formats (PDF, DOCX, HTML, Markdown) using AI-powered transcription.

AI Processing and Third-Party Services

Your uploaded documents are processed using third-party AI services to perform transcription. Currently, we use services provided by Anthropic and Google. This means:

• Document content is transmitted to these providers solely for the purpose of generating your transcription
• We do not use your documents to train AI models. Third-party providers operate under their own data policies, which you can review on their respective websites
• An anonymous account identifier is shared with providers for abuse monitoring purposes. This identifier cannot be used to determine your name, email, or other personal information

Account Responsibilities

You are responsible for:

• Maintaining the confidentiality of your account credentials
• All activity that occurs under your account
• Providing accurate account information

Acceptable Use

You agree not to:

• Upload content that infringes on others' intellectual property rights
• Use the service for any unlawful purpose
• Attempt to interfere with or disrupt the service
• Circumvent any access or usage limits
• Upload content designed to manipulate, exploit, or probe AI processing systems
• Upload illegal, harmful, or abusive content
• Upload documents containing personally identifiable information, protected health information, or other sensitive personal data. AccessibleNotes is designed for academic content — lecture notes, problem sets, study materials — not personal records
• Attempt to extract system prompts, training data, or other proprietary information from the AI systems used by the service

Content Monitoring

We may review uploads and generated outputs to enforce these terms, ensure the quality of our service, and improve our products. We may also review content flagged by our systems or by third-party AI providers. If content uploaded through your account violates these terms or a provider's usage policies, we may take action including suspension or termination of your account.

Intellectual Property

You retain full ownership of all content you upload and all documents generated from your content. We claim no rights to your materials.

Data Handling

• Uploaded documents are stored in our systems for processing and are retained so you can access your transcriptions
• Documents transmitted to AI providers for processing are subject to those providers' respective privacy and data handling policies
• You may delete your documents and transcriptions at any time through your account settings

Service Limitations

• AccessibleNotes is a tool to assist you in producing accessible documents — it does not take over your obligation to verify the final result. Transcription accuracy depends on handwriting legibility and document quality; AI-generated content should always be reviewed and edited before sharing
• You are responsible for verifying that transcriptions are accurate, complete, and meet your accessibility requirements before distributing them. Exported documents should be tested with appropriate tools (e.g., screen readers, PDF accessibility checkers)
• Service availability may be interrupted for maintenance or due to circumstances beyond our control

Payment and Billing

Payments are processed by a third-party payment provider. By subscribing, you agree to their applicable terms of service.

Subscription Plans

• Accessible Notes is offered as an annual subscription
• The subscription includes a weekly page quota that resets every Sunday at midnight UTC
• Each page of a document you process counts as one page toward your weekly quota
• See Plans & Pricing for current plan details and pricing

Free Pages

• Every account includes 100 free pages for use without a subscription
• Free pages do not expire
• Free pages are consumed when documents are processed outside an active subscription period
• Once free pages are exhausted, a subscription is required to continue processing documents

Refund Policy

We offer a full refund within 30 days of any payment, no questions asked. After 30 days, subscription payments are final.

If you experience a technical issue that prevents the service from working as intended, contact support@normalthought.com and we will make it right.

Termination

We may suspend or terminate your account if you violate these terms. You may delete your account at any time. Upon termination, your data will be deleted in accordance with our Privacy Policy.

Limitation of Liability

AccessibleNotes is provided "as is" without warranties of any kind. To the maximum extent permitted by law, we shall not be liable for any indirect, incidental, or consequential damages arising from your use of the service.

Governing Law

These terms are governed by the laws of the State of Delaware, United States.

Changes to These Terms

We may modify these terms at any time. Continued use of the service after changes constitutes acceptance of the modified terms. We will notify registered users of material changes via email.

Contact

For questions about these terms, contact us at legal@normalthought.com.

Accessibility Statement

Last updated: February 27, 2026

Our Commitment

AccessibleNotes, operated by Normal Thought Technologies LLC, is built with accessibility at its core. Our mission is to make handwritten content accessible to everyone, and we hold ourselves to the same standard for our own application.

Conformance Goal

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. We regularly test our application and work to address any accessibility barriers.

Accessibility Features

• Semantic HTML with proper heading hierarchy
• ARIA labels and landmarks for screen reader navigation
• Skip-to-content navigation link
• Keyboard-navigable interface
• Sufficient color contrast ratios
• Responsive design that works across devices and zoom levels

Known Limitations

We are continuously improving. If you encounter accessibility barriers, please let us know so we can address them.

Feedback

We welcome your feedback on the accessibility of AccessibleNotes. If you encounter any barriers or have suggestions, please contact us:

• Email: accessibility@normalthought.com

We aim to respond to accessibility feedback within 5 business days.