Are you adjusting the charging amperage on both the vehicle AND the L2 charger to ensure they are matched up? Which charger are you using? What were the L2 output amps set at prior to the OTA update being installed? This should resolve itself once you ensure both the charger and vehicle amp settings match up.
In the past the Rivian was always set at 48. My L2 is 40. I never had to touch anything and it would charge regardless without tripping the breaker. Only this update has started to cause it to trip. I’ve even did a hard reset to no avail.
It does not read texts on the vehicle screen. It's enabling you to share any address that you can view on your phone that is in plain text format to the vehicle's nav via the app. Say someone texts you an address or you view an address on a website that isn't formatted as a link, just "123 North Ave etc" you can simply highlight that text address in your phone and "share" it to the Rivian app and have your nav pick it up to route to it automatically.
Or at least provide an accessible link to the CHANGELOG.MD file in github, which it appears they have not updated yet...
Why would some random Rivian customer's github repository be the source of truth? Rivian certainly is never going to post a link to something like that.
I doubt the error was intentional or that it rises to the level of "heinous crime". Your highlighted text appears to be a placeholder. My guess is that someone forgot to go back and insert a better description. No one else noticed before it was submitted. I'm sure they'll fix it on the next go round.This is one of the more heinous crimes against accessibility I've seen in a while.
I think the meta point here is that there's no good text description of an image of pages of text besides... all the text. At which point you should just post the text, not the image.
You're right that many screen readers can do OCR (and browsers increasingly have some of this support built in - literally something my team works on). It's still sub-optimal for lots of reasons, primarily because it has limited ability to infer semantic aspects of layout (headings, bullets/lists, formatting, etc.).
I think this repo is a community project, which is a great example of another audience hurt by the release notes being an image. Now somebody has to OCR or retype/reformat all that to update the community changelog, instead of just copying and pasting.
