Accessibility Statement
What we have actually built for riders using a keyboard, a screen reader, magnification or reduced motion, where the gaps still are, and how to tell us when something blocks you.
Best Limos of Myrtle Beach is a blind bid marketplace for chauffeured transportation across the Grand Strand of South Carolina. Booking a ride should not depend on how you read a screen, whether you can use a mouse, or how much motion your body tolerates. This statement sets out what we have built, what we test, what we know is imperfect, and how to reach us if something on this site stops you from posting a trip.
Accessibility statements have a bad habit of listing aspirations. This one lists features you can go and use right now, because a promise about future work is no help to somebody trying to request a wedding car tonight.
The Short Version
1. Our Commitment and the Standard We Build To
We aim to conform to the Web Content Accessibility Guidelines, version 2.1, at Level AA. That is the standard most public bodies and courts in the United States treat as the practical benchmark, and it is the one we design and code against.
We are not going to claim perfect conformance. This is a large site built quickly, and any honest developer will tell you that a site of this size drifts as pages are added. What we will claim is that accessibility was designed in rather than bolted on, that every template shares the same tested components, and that we treat a reported barrier as a defect rather than a suggestion.
2. The Accessibility Panel on Every Page
Look for the accessibility icon fixed in the corner of every page, on every device. It opens a panel of display controls that change how the site renders for you. The button is reachable by keyboard, it reports whether the panel is open, and each control reports whether it is currently on.
| Control | Effect | Useful for |
|---|---|---|
| High contrast | Switches to a black background with white body text and stronger borders on cards, forms and answers | Low vision, glare, older screens |
| Larger text | Steps the base text size up twice, then back to normal. The label changes to tell you which step you are on | Small type, reading at a distance |
| Dyslexia friendly font | Swaps the body typeface for a plain sans serif and widens letter and word spacing | Dyslexia, reading fatigue |
| Underline links | Forces an underline on every link so links never rely on colour alone | Colour vision differences |
| Reduce motion | Turns off animations, transitions and smooth scrolling, and pauses the homepage hero video | Vestibular disorders, motion sensitivity |
| Reset all | Clears every choice and returns the site to its default appearance | Shared or public computers |
Your selections are saved in your browser's local storage, so they carry from page to page and from visit to visit without any account or login. That data stays on your device and is never sent to us; the privacy policy covers it under functional storage. Clearing your browser data resets the panel, which is worth knowing if your settings ever disappear.
3. Keyboard Navigation and Visible Focus
Everything on this site can be operated without a mouse. Menus open from the keyboard and close when focus leaves them, so you are never trapped inside a dropdown. The Escape key closes any open navigation panel and the accessibility panel.
Focus indicators are deliberately loud. Links, buttons, form fields and select menus draw a two pixel outline with an offset gap when they receive keyboard focus, which is a visible ring rather than the faint default some browsers apply over a dark background. We do not remove focus styling anywhere, and the segmented trip type control shows its own outline so you can see which option you are about to choose.
The first thing the Tab key reaches on any page is a skip link reading "Skip to main content". It stays off screen until it takes focus, then appears at the top left. Activating it jumps past the header and the two navigation menus straight to the page content, which saves a keyboard user roughly thirty stops on every single page.
4. Structure, Landmarks and Headings
Pages are built from real HTML landmarks rather than styled containers: a header region, a single main region, a footer, and navigation regions that carry their own labels so a screen reader can tell the breadcrumb apart from the quick action bar at the bottom of a phone screen.
Every page carries exactly one first level heading and steps down through heading levels in order, without skipping. Lists are marked up as lists, tables of comparison data use proper header cells with scope attributes and a caption describing what the table shows, and the question and answer accordions on service pages are native disclosure elements that expand and collapse from the keyboard with no scripting required.
5. Images, Text and Colour
Photographs that carry meaning have descriptive alternative text that says what is in the frame rather than repeating the file name. Decorative images, mainly the large photographs behind page headers, are marked as decorative and hidden from screen readers so they are not announced as noise. Inline icons that sit next to a text label are hidden the same way, because the label already says what the icon means.
The site's default palette is a dark theme with gold and silver accents, chosen and adjusted so body text and interface labels hold their contrast against the background. Colour is never the only way information is conveyed: links are distinguished by underline as well as colour, form errors change the field border rather than only the text tint, and the high contrast mode is available for anyone who needs more separation than the default provides.
6. Motion, Animation and the Homepage Video
If your operating system is set to reduce motion, this site respects that automatically. Animations and transitions are switched off, smooth scrolling reverts to an instant jump, hover effects that would move a card stay still, and the looping video behind the homepage header is paused rather than played.
You do not have to change a system setting to get that behaviour. The reduce motion control in the accessibility panel does the same job for this site alone, and the homepage video responds to it the moment you press it. Whichever route you take, the video is muted, it carries no audio track to interrupt a screen reader, and no content is lost by pausing it.
7. Reading the Site in Another Language
The language control sits in the bar at the top of every page and offers twelve languages, including Spanish, French, German, Portuguese, Chinese, Japanese, Korean, Russian, Arabic and Hindi. It is a standard select menu with a label that is present for screen readers even though it is visually hidden, so it announces its purpose rather than reading as an unlabelled combo box.
Translation is machine generated. It is genuinely useful for understanding a page, and it is not a substitute for content written in your language. Returning to English clears the translation and reloads the page.
8. The Bid Request Form
The three step bid request form appears on every page of this site, and it is the one interaction that matters most, so it gets extra attention. Every field has a visible label tied to it, not a placeholder standing in for one. The trip type choice is a grouped set of radio buttons with a legend describing the group. Required fields are marked as required in the markup, not only in colour.
When you submit, the confirmation message is announced by screen readers rather than appearing silently, because a status message you cannot see is no confirmation at all. Progress through the three steps is described in text as well as in the progress bar. If any part of the form is still awkward for you, you can message us directly by a route that reaches the same people, and you can describe a trip there in plain sentences.
9. Known Limitations
Being straight about the gaps is more useful than a blanket claim of conformance. Here is what we know.
- Third party embedded content. Google Translate and Google Maps load code we do not write and cannot rewrite. Their controls, their keyboard behaviour and their contrast are set by Google. We isolate them where we can, label our own wrapper controls, and keep every essential piece of information available in the page itself rather than only inside a map.
- Machine translation. Translating a page rewrites the text in place. Wording chosen for clarity, and the pronunciation a screen reader gives it, may both suffer. English remains the authoritative version of every policy document on this site.
- Wide comparison tables. Tables with several columns scroll sideways inside their own container on narrow screens. That keeps the page itself from scrolling horizontally, but it does mean some tables need a swipe or an arrow key press to read in full.
- Headings that scale to fit. Large headings are sized by script to fill their container. They respond to browser zoom and to the larger text setting, but on very unusual window sizes a heading may briefly render at an awkward size before it settles.
- Operator supplied material. Once bids and vehicle photographs from independent operators are live, some of that content will come from third parties. We will hold operators to alternative text requirements, and we will not be able to guarantee every submission on the day it arrives.
10. How We Test
Testing here is routine rather than ceremonial. Every template is walked through with the keyboard alone, from the skip link to the last footer link, checking that focus is always visible and that nothing traps it. Pages are checked with browser zoom raised and with each accessibility panel option switched on, including combinations such as high contrast with the largest text, because settings interact.
We run automated checks in the browser for missing labels, heading order, contrast and duplicated element identifiers, and we treat the results as a starting point rather than a score, since automated tools catch a minority of real problems. Any change to a shared component, the header, the footer, the accessibility panel or the bid form, triggers a fresh pass across a sample of pages. We have not commissioned an independent audit, and we will say so here when we do.
11. Reporting a Barrier
If any part of this site blocks you, we want to hear about it, and we would rather hear about a small annoyance early than a serious barrier after somebody has given up.
If you need help posting a trip while a barrier is being fixed, say so in the same message. Describe the occasion, the date, the pickup point, the destination and the number of passengers, and we will get the request into the marketplace for you so operators can bid on it. That path is always open, and it costs nothing, which is the same deal everybody else gets through the standard bidding process.
12. Changes to This Statement
This statement is reviewed whenever the site's shared components change and whenever a reported barrier leads to a fix worth documenting. The date at the top of the page changes with it. As the booking and ratings systems move out of the current build, this page will be updated to cover the accessibility of those features rather than left describing a site that no longer exists.
Post a Trip Using Whatever Works for You
Keyboard only, screen reader, magnified, translated or with motion switched off: the form below behaves the same way. Tell operators what you need in the route field and they will price it.
Prefer to write it out in sentences? Send it through the contact form instead, or read the site wide question list first.
Start Your Free Bid Request
Takes about 90 seconds. Operators bid, you decide.