php 工具箱 内网访问_PHP工具中的可访问性状态

php 工具箱 内网访问

Usually when I tell people that I’m blind, many people ask me how I can use the computer. “Is someone reading you my messages?” I remember someone asking. Many people imagine that I have this super-nifty speech recognition software that I can just talk to, and it would do anything, even write code. Imagine dictating code to a speech recognition system!

通常，当我告诉别人我失明时，很多人会问我如何使用电脑。 “有人在读你我的信息吗？” 我记得有人问。 许多人认为我拥有可以与之交谈的超级灵巧语音识别软件，它可以做任何事情，甚至可以编写代码。 想象一下语音识别系统的听写代码！

I gave an answer on Quora, to someone who had asked How does a visually impaired computer programmer do programming? I recommend you go through that answer to have a better context on what I’ll be talking about in this post. As is my habit, though, I’ll still point out the important bits here, so if you don’t feel like clicking on that link, don’t worry!

我对Quora的回答是，有人问过视障计算机程序员如何进行编程？ 我建议您仔细阅读该答案，以使我对本文中要讨论的内容有更好的了解。 不过，按照我的习惯，我仍然会在这里指出重要的一点，因此，如果您不想单击该链接，请不要担心！

Before I get to the comparison, allow me to give you a few facts so that we are all on the same page. Feel free to skip forward if you already know these points, but I’ve found that a lot of people don’t, and I’m going to start with those.

在进行比较之前，请允许我提供一些事实，以便我们都在同一页面上。 如果您已经知道这些要点，请随时跳过，但是我发现很多人不知道这些，我将从这些开始。

盲人如何使用计算机？ (How do the blind use computers?)

They use screen readers. As the name implies, these applications read the screen through synthesized speech, and they also have an optional Braille output through a Braille display. Both of these options (speech and Braille) have to go through the screen reader, though, so if the screen reader can’t see the content, it can’t display it through either of these outputs.

他们使用屏幕阅读器 。 顾名思义，这些应用程序通过合成语音读取屏幕，并且还具有通过盲文显示器输出的可选盲文。 不过，这两个选项(语音和盲文)都必须通过屏幕阅读器，因此，如果屏幕阅读器看不到内容，则无法通过这两个输出之一显示内容。

您如何输入？ 您如何使用鼠标？ (How do you type? How do you use the mouse?)

The answer to both these questions is, “through the keyboard”. Our screen readers have very specialized keystrokes that allow us to move the mouse, click, hover on an item, and jump around in web documents (by links, h1-6 headings, lists and list items, form fields and many more).

这两个问题的答案都是“通过键盘”。 我们的屏幕阅读器具有非常专业的按键，使我们能够移动鼠标，单击，将鼠标悬停在某个项目上，以及在Web文档中跳转(通过链接，h1-6标题，列表和列表项，表单域等等)。

听起来很厉害！ 这是否意味着您无法使用计算机进行任何操作？ (Sounds very powerful! Does this mean there’s nothing you can’t do with a computer?)

I wish. No.

我希望。 没有。

Why? The reasons, as in almost everything else, range from irresponsible people to the lack of time and information. After all, the disabled are but a minority, and their voice is not as loud as, say, the people who call for the native support of the latest shiny PHP framework. The problem is that screen readers use low-level APIs to give them information on the window. They ask the browser, or in terms of desktop applications, the operating system, to tell them what kind of control or window they are dealing with. Is this item that has just gained focus a text box, or is it a check box? What is its value, and its label? What is its state (i.e. is it checked or unchecked, selected or unselected)?

为什么？ 与几乎所有其他原因一样，原因从不负责任的人到缺乏时间和信息。 毕竟，残障人士只是少数，他们的声音并不像要求最新的闪亮PHP框架本地支持的人那样响亮。 问题是屏幕阅读器使用低级API在窗口上提供信息。 他们要求浏览器，或者就桌面应用程序而言，操作系统，告诉他们正在处理哪种控件或窗口。 这个刚刚获得关注的项目是一个文本框，还是一个复选框？ 它的价值和标签是什么？ 它的状态是什么(即它是选中还是未选中，选中还是未选中)？

简要介绍Web应用程序世界 (A Brief Detour to the World of Web Applications)

This kind of API was simply not available for the web until the last few years when the WAI-ARIA was published by the World Wide Web Consortium (W3C) and later on became a standard recommendation on march of 2014. Before that time, there was no information on how to make accessible, custom client-side elements, or client-side updates.

直到最近几年，万维网联盟(W3C)发布了WAI-ARIA ，并在2014年3月成为标准建议之后，这种API才在网络上完全不可用。没有有关如何进行可访问的，自定义客户端元素或客户端更新的信息。

For example, a lot of people use a span element to create a custom button. Screen readers recognize this element as static text, as it is not a button, or an input of type submit. However, for someone sighted, it’s styled like a button, it acts like a button, and it even stays down like a button (for toggle buttons).

例如，许多人使用span元素创建自定义按钮。 屏幕阅读器识别此元素为静态文本，因为它不是一个按钮 ，或类型的输入 提交 。 但是，对于有视力的人来说，它的样式就像一个按钮，它的作用就像一个按钮，甚至像按钮一样停留(对于切换按钮)。

What web developers can do at this point is to explicitly mention that a span is a button, by using the button role. The code is so simple, many people can’t believe it:

此时，Web开发人员可以做的就是通过使用button角色来明确提及span是一个按钮。 代码是如此简单，很多人不敢相信：

<span class="button danger" role="button">Self-destruct!</span>

Done. Through this cosmetic change that wouldn’t take more than ten seconds (I’m counting eight seconds for hunting down the button), you’ve made your application easier to use for thousands. Isn’t it worth the effort?

做完了 通过这种花费不到十秒钟的外观更改(我正在计算八秒钟来按下按钮)，您已经使成千上万的应用程序易于使用。 值得付出努力吗？

Note: If you want to know more about web accessibility (I hope that you do), you can get a very in-depth coverage of many topics at the WebAIM articles page.

注意 ：如果您想了解更多有关Web可访问性的信息(我希望您可以这样做)，那么您可以在WebAIM文章页面上非常深入地讨论许多主题。

IDE中的可访问性状态 (The State of Accessibility in IDEs)

With more than one billion disabled people in the world, and most of them unemployed, those with disabilities don’t need any favors or for people to pity them – they just need a level playing field, which can be created by making applications just as accessible to them as others. This holds especially true for applications that are tied to employment. Tools such as IDEs may not be essential for everyone, but they certainly increase the productivity of many people, and when you are disabled, you need to be fast. You need to be a great learner and doer, or your existence for a company serves no purpose and you’re out of your job. I’ve heard many people complain about the unfairness of this approach, but I’m sure we all can agree that no one has the time to babysit, especially not in a technical environment.

世界上有十​​亿残疾人 ，其中大多数人失业，残疾人不需要任何帮助，也不需要人们同情他们–他们只需要一个公平的竞争环境，就可以通过创建应用程序来创建和其他人一样容易获得。 对于与就业相关的应用尤其如此。 诸如IDE之类的工具可能并不是每个人都必不可少的，但是它们肯定会提高许多人的工作效率，并且当您被禁用时，您需要快速。 您需要成为一个出色的学习者和行动者，否则您在一家公司的存在毫无目的，而您就失业了。 我听到很多人抱怨这种方法的不公平，但是我敢肯定，我们所有人都可以同意，没有人有时间保姆，特别是在技术环境中。

With that said, let’s look at the most-favored tools of our own industry one at a time. I will be referring to the survey done by SitePoint for the Best PHP IDE in 2014, and the question we will be seeking to answer is: how friendly is web development for the people who are blind and thinking of using an IDE to speed up their learning process, workflow, or both?

话虽如此，让我们一次来看一下我们行业中最喜欢的工具。 我将参考SitePoint 在2014年进行的关于最佳PHP IDE的调查，我们将要回答的问题是：对于盲人和正在考虑使用IDE来加快其开发速度的人们来说，Web开发的友好程度如何？学习过程，工作流程或两者？

I will give each IDE a score of between one to four for the following points:

对于以下几点，我将给每个IDE评分在1-4之间：

• Essential features: is the editor accessible? What about the menus and the title bar?
  基本功能：编辑器可访问吗？ 菜单和标题栏呢？
• Assistance features: how much can a blind developer be assisted by this IDE while coding? Are code completion, PHP documentation, and PHPDoc pop-ups accessible?
  辅助功能：在编写代码时，此IDE可以为盲人开发人员提供多少帮助？ 是否可以访问代码完成，PHP文档和PHPDoc弹出窗口？
• Supplementary features: What about the non-essential features, like integration with Git, the console, debugging, and so on?
  补充功能：非必需功能如何处理，例如与Git集成，控制台，调试等？
• Community engagement: have they responded to issues/comments?
  社区参与：他们是否对问题/评论做出了回应？

第一：PHPStorm (Number One: PHPStorm)

We all know that PHPStorm is a really good IDE. It has near-instant support for new frameworks and technologies such as Laravel and HHVM, it has very nifty features for renaming, moving, and refactoring that take care of a lot of nitty-gritty details like changing namespaces, and its attempts at guessing variable types are mostly successful.

我们都知道PHPStorm是一个非常好的IDE。 它对Laravel和HHVM等新框架和技术提供了近乎即时的支持，它具有用于重命名，移动和重构的非常漂亮的功能，可以处理很多细节问题，例如更改名称空间以及尝试猜测变量。类型大多是成功的。

In terms of accessibility, though, I’m afraid PHPStorm gets a score of – wait for it – zero!

但是，就可访问性而言，恐怕PHPStorm的得分-等待它-零！

Yes! The main window is not accessible, and when this feature is not available, neither are the others. If you look at the accessibility issue, you will see that their team hasn’t responded with any updates to this issue at all. I urge you to upvote that issue, so that it may be noticed by their team.

是! 主窗口不可访问，并且当此功能不可用时，其他窗口也不可用。 如果您查看可访问性问题 ，您将看到他们的团队根本没有对此问题进行任何更新。 我敦促您赞成该问题，以便他们的团队注意到。

第二名：SublimeText (Number Two: SublimeText)

Ah, the bliss of having a multi-platform, lightning-fast lightweight IDE that can be customized by using a large number of plugins. One of the people I was interviewing for my current job would even go so far as to say, “everyone in your company must use SublimeText.”

啊，拥有多平台，闪电般快速的轻量级IDE的幸福，可以通过使用大量插件进行自定义。 我正在为我目前的工作面试的人之一甚至会说：“公司中的每个人都必须使用SublimeText。”

And yet, this bliss is also denied to the prospective PHP programmer. This IDE also gets a zero, because nothing in it is accessible to screen readers, and the UserEcho thread for accessibility hasn’t gotten any responses from their core team.

但是，这种幸福也被潜在PHP程序员所拒绝。 该IDE也为零，因为屏幕阅读器无法访问其中的任何内容，并且可访问性的UserEcho线程尚未获得其核心团队的任何回应。

第三名：NetBeans (Number Three: NetBeans)

NetBeans is famous for its cool snippet generation capabilities, and its “quick-fix” functionality which does a lot of things for you automatically. The bug reporting feature is also very cool.

NetBeans以其出色的代码片段生成功能和“快速修复”功能而闻名，该功能可以自动为您完成许多工作。 错误报告功能也很酷。

Accessibility wise, NetBeans is a bit better. I can navigate in the code, although with a lot of extra keystrokes as it keeps moving my screen reader’s focus to the Navigator. However, I have been hearing good things about the efforts of the Quorum project and apparently, NetBeans is going to have extra accessibility features soon.

在可访问性方面，NetBeans更好一些。 我可以在代码中导航，尽管有很多额外的按键输入，因为它一直将屏幕阅读器的焦点移到Navigator上。 但是，我一直在听到有关Quorum项目所做的努力的好消息，而且显然，NetBeans将很快具有额外的可访问性功能。

第四名：基于Eclipse的IDE(Zend Studio，Eclipse PDT) (Number Four: Eclipse-based IDEs (Zend Studio, Eclipse PDT))

I’ve always heard that Zend Studio and Eclipse PDT are nowhere as good as PHPStorm. At work, all my colleagues use PHPStorm. While I agree with their assessment, Zend Studio has something for me that PHPStorm doesn’t have: it’s accessible.

我一直听说Zend Studio和Eclipse PDT不如PHPStorm好。 在工作中，我的所有同事都使用PHPStorm。 虽然我同意他们的评估，但Zend Studio对我来说有些PHPStorm没有的东西：可以访问。

The code editor window and all other windows are accessible. The autocompletions or code assist suggestions are accessible, and so is documentation. Even the annotations (for example, why Zend has drawn a red line under your line of code) are accessible. Zend Studio and Eclipse PDT are both the most accessible IDEs I have ever used.

可以访问代码编辑器窗口和所有其他窗口。 自动完成或代码辅助建议可访问，文档也可访问。 甚至注释(例如，为什么Zend在您的代码行下画一条红线)都可以访问。 Zend Studio和Eclipse PDT都是我使用过的最易访问的IDE。

To be fair, though, Zend Studio and Eclipse PDT both owe their accessibility to the Eclipse team. Eclipse has been accessible for years, and they take accessibility very seriously. However, since we’re rating accessibility here and not development teams, Zend Studio and Eclipse PDT get a resounding four!

公平地说，Zend Studio和Eclipse PDT都应归功于Eclipse团队的可访问性。 Eclipse已经可以访问多年了，他们非常重视可访问性。 但是，由于我们在这里对可访问性而不是开发团队进行了评估，因此Zend Studio和Eclipse PDT的得分是惊人的四个！

Eclipse even has a page, Accessibility Features for Eclipse that gives blind and visually impaired users more tips on how to use Eclipse and Eclipse-based IDEs.

Eclipse甚至还有一个页面，即Eclipse的辅助功能，该页面为盲人和视障用户提供了有关如何使用Eclipse和基于Eclipse的IDE的更多技巧。

第五名：记事本++ (Number Five: Notepad++)

I consider Notepad++ an editor, and not an IDE. It is nowhere as customizable as SublimeText, and nowhere as big as PHPStorm and Zend Studio in terms of memory and CPU consumption. It’s awesome for when you have to edit a piece of code and you know perfectly well the functions you will be calling, or the values you will be setting.

我认为Notepad ++是编辑器，而不是IDE。 在内存和CPU消耗方面，它没有SublimeText可自定义的地方，也没有PHPStorm和Zend Studio大。 当您必须编辑一段代码并且完全了解要调用的函数或要设置的值时，它真棒。

The Notepad++ windows and options are all accessible – that is, the essential features. The non-essential features aren’t accessible, though. Things such as autocompletions and errors are not announced by screen readers.

Notepad ++窗口和选项都是可访问的-即基本功能。 但是，非必需功能无法访问。 屏幕阅读器不会宣布诸如自动完成和错误之类的事情。

Over the years, though, Notepad++ has become more accessible in overall usage. There have been responses and cosmetic changes, but when you compare their community engagement with the top two IDEs above, they have been a lot more engaged. I give this editor a two – one for essential features, and one for community engagement.

但是，多年来，Notepad ++在整体用法上变得更加易于访问。 已经做出了回应，外观发生了变化，但是当您将他们的社区参与度与上面的前两个IDE进行比较时，他们的参与度要高得多。 我给这个编辑器两个选项，一个用于基本功能，另一个用于社区参与。

结论 (Conclusion)

The PHP landscape is not bright and sunny in terms of accessibility. Whereas the sighted have the option of choosing between free and paid IDEs, the best IDE in terms of accessibility are Eclipse-based editors. While this is much better than nothing, it leaves a lot to be desired. Technology is for everyone, and we should strive to make it so.

就可访问性而言，PHP的前景并不乐观。 有见识的人可以在免费和付费IDE之间进行选择，而就可访问性而言，最好的IDE是基于Eclipse的编辑器。 尽管这总比没有好，但还有很多需要改进的地方。 技术适合每个人，我们应该努力做到这一点。

翻译自: https://www.sitepoint.com/the-state-of-accessibility-in-php-tools/

php 工具箱 内网访问