You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
@mix %uRipPh1WlOflD+hetNuNR3otfI+22PFTUuGNx4nPz9c=.sha256

I'm really excited for this. I'm looking at the toolbar in the top right of Patchbay and thinking - I could put an accessibility widget in there ... kinda like a firefox extension

Here's a link to the css-tricks primer on filter styles ... really amazing.
You can change hue and blur content event !

@mix %m3BYoT/Vymeu08LaHvzW0k1YSAfUE3RAEoftvc9I8Gc=.sha256

@Teq I'm keen to keep momentum on this and get to a working prototype ASAP. The idea is make something a bit simple, and maybe a bit ugly that works and then use it and then tweak it some.

I reckon depending on time commitments, we can get something within the next 2 weeks. If the pace is ever to fast lets just keep in touch about where we're at :heart:

User has not chosen to be hosted publicly
@mix %rRXOrdKgonaRIha//tYireZg0nkGyYFjGixKDUkyoeA=.sha256

This is an awesome breakdown, and it's already covered a few things I'd not ever considered.

I think there are 2 layers you're designing for here :

  • changing a particular attribute
  • laying out the controls in a manageable way

What I'd like to request is that you choose the 2-3 attributes that are most relevant to you, and have a go at a simple control interface that you'd like. We can both have a couple of goes and decide what to start with in terms of layout / interface.

Then I'll biuld it and you an use it for a week. Given your above thinking I'll be careful to make the code granular underneath as I build so that we can more easily address the needs you've illustrated above in future improvements and additions.
Note I could potentially build both interfaces above, because how people categorise and think is another accessibility thing right!

But let's not solve all the cases at the outset, otherwise it will take a long time before we can validate things with some experimenting and use. This approach is some hard learned software / startup culture. It's a fairly strong preference about how to go about this, and I'm aware it might be different to the culture you're situated in, so let me know if it sounds off.

User has not chosen to be hosted publicly
@mix %ltAyNUSbC0Cq0jZkrDS49oOktlBY5pzFIFTwr4fDa7o=.sha256

ok invert colors is easy. the test description for images is more challenging to code (than, e.g. contrast/ saturation/ hue, or brightness of all images).

Hiding images is easy, it's unhiding them when you click which might take a bit of work ... oh actually I can think of an easy workaround for unhiding all the images in a particular block message ...
Is the text description about reducing the visual weight of a page, or is it the brightness of images, or something else?

With the "text description" would that just be the file name, so you would see in the page a placeholder like :


                     Scamp1_teq.JPG


.
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@mix %DOtRc4Hd/sLoAB3ZXf4Ze8WnbdjdN3T7CVWOxu906X4=.sha256

thanks for that context. Screen readers are gonna be a whole thing, but are a great long term goal.
Technically the hidden image is a stretch, but that's good - it's good to build what's needed and not what's easy. I'm reading into what I can do tidily now.

Color inversion is gonna be easy.
Other fancy solutions for the future could include assessing the 'brightness' of an image and tuning the super bright white ones automagically. Haven't done that before, and not sure how processor intense it is, but also a possibility. (SHH mix, stop getting excited by what you can do and focus on what you can do now)

@mix %dmP8wpIjDZ+JjX/9A101AjHWaVoFRQ3jch1GJbMVDdk=.sha256

I've not forgotten about this @teq, I've been looking for a reproduceable way to do the image hiding in my spare bits of time. I'm researching it now while I ride the bus.

User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
Join Scuttlebutt now