Live data from Hacker News

Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

github.com

81–90 of 107 posts

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#81
post #74
post #71

Earlier quoted context omitted.

> Accessibility as afterthought, as always. You are in a minority. Minorities are always an afterthought. It's hard meeting the needs of every single minority - there are so many with many diverse needs.

Yes, being in the small group that wants people to actually use proper accessible markup as WCAG indicates does put me in a minority, it's true. However, this concept that there are a lot of minorities so obviously we can't cover all the bases seems a little silly. Do people of color need different markup? Do women require somebody adds special javascript libraries so they can access the content? Making content acces…

>Just like the site isn't done until it renders in IE 11, it's not done until it reads with NVDA.

Interesting opinion. I'd argue that it's not at all a web developer's job to comply with every single accessibility guideline or support outdated browsers, unless required by their contract and paid for by whoever commissioned the work. These requirements are part of the reason that most governmental contracts are overpriced by a factor of 10 (the other reason being corruption).

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#82
post #34

But this is built with React so its not really reusable outside of its ecosystem. Is there a version that would run on preact instead? Maybe QuillJS would be a better option for general purpose editor.

If you use preact without preact-compat then you seal yourself into the preact ecosystem. That's why preact-compat exists.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#83
post #61
post #20

The high CPU and memory usage was due to a large gif which was included two times. This gif accidentally was 1280p with 20fps and was about 40mb large. For some reason, the resizer did not properly work. Anyways, the gif is now removed. I hope the performance gets much better now. The CPU fans on macbooks going up where probably due to a lack of a dedicated graphics card. This happened to me with my macbook and large…

This does not appear to work at all with my screen reader. Accessibility as afterthought, as always. I used to look forward to trying to help people fix their stuff to be accessible, but now I'm just tired of every single fucking thing somebody creates being broken for me because everything is a complete heaping pile of inaccessible garbage and nobody even thinks about accessibility. It's not like there aren't thousa…

This was something I really wish would be featured at every conference by device / OS manufacturers every year.

I was surprised there was no discussion of Android accessibility this year at IO.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#84
post #62
post #61

Earlier quoted context omitted.

This does not appear to work at all with my screen reader. Accessibility as afterthought, as always. I used to look forward to trying to help people fix their stuff to be accessible, but now I'm just tired of every single fucking thing somebody creates being broken for me because everything is a complete heaping pile of inaccessible garbage and nobody even thinks about accessibility. It's not like there aren't thousa…

It must really suck, and when I work on small(but large) personal projects I feel bad that someone might not be able to use it. What are some good resources to start thinking accessibility first? I remember in the past it was .. a project and a half in and of itself.

This is only one small facet of the problem, but a11y[0] is a helpful tool to automate accessibility testing. It of course doesn't cover everything you should be concerned about, but as someone who's far from an expert, it feels like a good starting point.

[0] https://github.com/addyosmani/a11y

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#85
post #74
post #71

Earlier quoted context omitted.

> Accessibility as afterthought, as always. You are in a minority. Minorities are always an afterthought. It's hard meeting the needs of every single minority - there are so many with many diverse needs.

Yes, being in the small group that wants people to actually use proper accessible markup as WCAG indicates does put me in a minority, it's true. However, this concept that there are a lot of minorities so obviously we can't cover all the bases seems a little silly. Do people of color need different markup? Do women require somebody adds special javascript libraries so they can access the content? Making content acces…

It is unfortunate that the effort spent to accommodate screen readers is easy to see as less rewarding than the effort invested into all of the other users... Truthfully, it seems like the only really good solution would be to make screen readers much better at understanding the content than to make the content much better at being understood by screen readers. Pool the expertise where the need is. This kind of thing is why I feel that good AI is so important. We can make information far more accessible, especially when you consider that the AI doesn't actually have eyes either.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#86
I went here: http://www.ory.am/sites/

They have a signup page. The premium option is $9/mo. I tried to signup, it brought me to a Google form. I completed the form.

OP: I will pay you $8/mo for this. It is beautiful and interesting, and is worth looking in to. I want to try to create some sites with this, I am happy to pay for it and self-host it. Hopefully it's easy to deploy.

Or better yet, I can let you host it for me. With the option of self-hosting anytime in the future. The key to adoption is making it as easy to install as Wordpress.

This could be big! Good luck.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#88
post #61
post #20

The high CPU and memory usage was due to a large gif which was included two times. This gif accidentally was 1280p with 20fps and was about 40mb large. For some reason, the resizer did not properly work. Anyways, the gif is now removed. I hope the performance gets much better now. The CPU fans on macbooks going up where probably due to a lack of a dedicated graphics card. This happened to me with my macbook and large…

This does not appear to work at all with my screen reader. Accessibility as afterthought, as always. I used to look forward to trying to help people fix their stuff to be accessible, but now I'm just tired of every single fucking thing somebody creates being broken for me because everything is a complete heaping pile of inaccessible garbage and nobody even thinks about accessibility. It's not like there aren't thousa…

Sorry for the late reply, but this condemning tone just really, really gets old.

This is a frigging open source project. Take it or leave it. If you want something, you send a frigging patch. Or you ask nicely.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#89
post #61
post #20

The high CPU and memory usage was due to a large gif which was included two times. This gif accidentally was 1280p with 20fps and was about 40mb large. For some reason, the resizer did not properly work. Anyways, the gif is now removed. I hope the performance gets much better now. The CPU fans on macbooks going up where probably due to a lack of a dedicated graphics card. This happened to me with my macbook and large…

This does not appear to work at all with my screen reader. Accessibility as afterthought, as always. I used to look forward to trying to help people fix their stuff to be accessible, but now I'm just tired of every single fucking thing somebody creates being broken for me because everything is a complete heaping pile of inaccessible garbage and nobody even thinks about accessibility. It's not like there aren't thousa…

Edit: Ahh I see you mentioned A11y or Ally, thought it was someone's user name.

Aside from using tab indexes to jump around on a page, what else helps?

Is Hacker News really good with accessibility?

Oh Screen Reader has that voice right? So proper use of Header tags... man how do you follow a chain of comments? control find and look for your user name? Oh maybe the threads part of Hacker News.

Aria tags...

Well probably good news for you with the move towards voice-interfaces with the Amazon Echo products and what not, maybe there will be API's or something to present data with voice-first in mind so no visual.

Post reply on HN